Can we add reference data in case statement in Computed content?
Solved
Can we use reference data in case statement in Computed content?
- Data Pioneer
Best answer by anna.spakova
Hi, apologies for the delay.
The Lists of values are covered by our documentation:Ā https://docs.ataccama.com/one/15.1.0/metadata-model/lists-of-values.htmlĀ Itās basically just a space from which you can add new values to your custom entities - the main goal for those is to serve as small lookups for drop-down properties in other entities. But you can have multiple properties in those value list entities and you can also populate them via API. In general, you can use any custom entity for a drop-down, this is just a pre-builtĀ example of how it can be done.
Since those lists are entities within the metadata model, they are reachable by the computed content.
Kind regards,
Anna
+3- Ataccamer
Hi ā
Ā
can you please elaborate a bit more on your usecase? The computed content is limited to the content of the mmm database, which means that it can only work with the metadata inside.
Kind regards,
Anna
- Data Pioneer
HI Anna, I have a table defined in One dataĀ
Ā
I want to use this in my case statement in Context to get value in attribute field. LIke where sensitivity is PII, mark as confidential. List is very long, so I don;t want to hard code in case. Rather use this One data table or any other reference table here
Ā
- Data Pioneer
My computed content looks like this:Ā
Ā
Ā with
Ā Ā connection_query asĀ
Ā Ā (select att.$attId$ Ā as term_instance_id,
Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā ti.$tiFrom$ as "term_instance_from",
Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā t.$tName$ Ā as "displayName",
Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā att.$attPath$ as "tiPath"
Ā Ā Ā Ā Ā Ā Ā Ā from $att$ att
Ā Ā Ā Ā Ā Ā Ā Ā inner join $ti$ ti on Ā att.$attId$ = ti.$tiParentId$
Ā Ā Ā Ā Ā Ā Ā Ā inner join $t$ t on ti.target_ri = t.$tId$ and
Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā (ti.target_rh is null or ti.target_rh = t.to_h)
Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā Ā join "_MmdDictionary" d on ti.$tiPath$ = d.id and d.name like '%/termInstances')
select j.term_instance_id as "id_i",
Ā Ā Ā Ā j.term_instance_from as "from_h",
Ā Ā Ā Ā $path("tiPath")$ as "path_i",
Ā Ā Ā Ā $type()$ as "type_i",
Ā Ā Ā Ā j.term_instance_id as "parent_id_i",
Ā caseĀ
Ā Ā Ā Ā Ā Ā when j."displayName"='DateOfBirth' then 'PII'
Ā Ā Ā Ā Ā Ā when j."displayName"='EmailAddress' Ā then 'PII'
Ā Ā Ā Ā Ā Ā when j."displayName"='FirstName' Ā then 'PII'
Ā Ā Ā Ā Ā Ā when j."displayName"='Mobile' then 'PII'
Ā Ā Ā Ā Ā Ā when j."displayName"='Landline' then 'PII'
Ā Ā Ā Ā Ā Ā else ''
Ā Ā Ā Ā Ā Ā end as "sensitivity",
Ā Ā Ā Ā Ā caseĀ
Ā Ā Ā Ā Ā Ā when j."displayName"='DateOfBirth' then '4 - High'
Ā Ā Ā Ā Ā Ā when j."displayName"='EmailAddress' Ā then '4 - High'
Ā Ā Ā Ā Ā Ā when j."displayName"='FirstName' Ā then '4 - High'
Ā Ā Ā Ā Ā Ā when j."displayName"='Mobile' then '4 - High'
Ā Ā Ā Ā Ā Ā when j."displayName"='Landline' then '4 - High'
Ā Ā Ā Ā Ā Ā else ''
Ā Ā Ā Ā Ā Ā end as "risk"
from connection_query j
+3- Ataccamer
Hi ā
I understand your usecase, but this isnāt supported to my knowledge. ONE Data is a completely different module that is separated from the mmm backend database, thus it cannot see itsĀ values. I am thinking that maybe the Lists of valuesĀ could be able to help you here instead of ONE Data but that has very limited functionality (no DQ monitoring etc.)
Also an alternative solution could be to use the orchestration server for this automation - you can export the ONE Data reference data into some DB and use this export in your workflow, that would populate the field via API. Together with some Notification handler you could potentially be able to make it ānear real timeā as well.
https://docs.ataccama.com/runtime-server/latest/workflow-and-scheduler/notifications-handler.html
Kind regards,
Anna
- Data Pioneer
Thanks for getting back. Can you share some screen shot of an example of List of values mentioned in first solution?
+3- Ataccamer
- Answer
Hi, apologies for the delay.
The Lists of values are covered by our documentation:Ā https://docs.ataccama.com/one/15.1.0/metadata-model/lists-of-values.htmlĀ Itās basically just a space from which you can add new values to your custom entities - the main goal for those is to serve as small lookups for drop-down properties in other entities. But you can have multiple properties in those value list entities and you can also populate them via API. In general, you can use any custom entity for a drop-down, this is just a pre-builtĀ example of how it can be done.
Since those lists are entities within the metadata model, they are reachable by the computed content.
Kind regards,
Anna
Hi ā
Login to the Ataccama Community
No account yet? Create an account
For Ataccama Customers and Partners
or
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.