topic Re: Metadata adjustments by sas code in Administration and Deployment

Metadata adjustments by sas code

Michael-K — Tue, 25 Feb 2025 08:53:08 GMT

This year's challenge is to create a clone of an existing metadata folder(around 800 objects). I can adjust the attributes of the data objects (names, paths, etc.) using SAS code (metadata_getnasn, metadata_getnattr, metadata_setattr).

So far I have failed at exchanging user written transformations in DI jobs. I suspect that this is possible with the
"metadata_setassn" function, but I can't find the way exchanging the association.

Have anyone already made such replacements and can you give me a tip? Or is this not possible with SAS code?

I would be very grateful for a short feedback and a hint in which direction I could continue my research.

Warm greeting, Michael

Re: Metadata adjustments by sas code

gwootton — Tue, 25 Feb 2025 19:34:16 GMT

I'm not clear on what exactly you are trying to do, but the METADATA_SETASSN function is passed an two URIs, that of the object whose association is being modified, and the object being associated. It is additionally passed the name of the association and a modification (append, merge, modify, remove or replace).

So, if I had an object "Object A" associated with a single object "Object B" through association "Assocation1", and I wanted to replace this association to "Object B" with one to "Object C" I could use METADATA_SETASSN with the REPLACE or MODIFY mod:
metadata_setassn(object-a-uri,"Assocation1","REPLACE",object-c-uri);
This replaces the association1 to object b with an assocation1 to object c.

If I wanted to retain the object b association I could use APPEND or MERGE to add an association to object c.

If I have multiple objects associated with object A through association1 and I want to replace B with C and leave the rest, I would use a REMOVE using the object-b-uri and APPEND or MERGE with object-c-uri, or I could use REPLACE and pass all the existing URIs except object-b-uri, instead adding the object-c-uri.

Re: Metadata adjustments by sas code

Michael-K — Wed, 26 Feb 2025 12:18:18 GMT

Thank you Greg for the quick reply. The explanations on how the functions "metadata_setassn" works are very helpful.

I'll try to create a little more understanding for our task with the following:

We need to clone (exportpackage -> importpackge) about 850 DI Jobs that contain user written transformations (hereinafter referred to as UWT). After cloning, in the jobs the original UWTs must be exchanged for the cloned UWTs .

As an example: in the source, the “Table_Source” table in the “Job_Source” job is linked to the user-written transformation “UWT_Source”.

After cloning, the “Table_Clone” table, which has also been cloned, is still linked to the UWT “UWT_Source”

Now we are looking for a way to convert the connection of the table “Table_Clone” to the also cloned UWT “UWT_Clone” with SAS code

The aim should be

As the UWTs are identical, the options and mapping should also be retained when replacing them.

Based on your explanation, I hope to make progress with the metadata_setassn function.
I would be very grateful for any further information

Best regards, Michael

Re: Metadata adjustments by sas code

gwootton — Wed, 26 Feb 2025 18:30:55 GMT

I'm not intimately familiar with how DI Studio job contents translate into Metadata objects so you may be best served by examining your "Job_Clone" object using the Metabrowse to see how these objects associate with each other, but I think in Metadata this is more complicated than switching out a single association.

Re: Metadata adjustments by sas code

Michael-K — Thu, 27 Feb 2025 06:51:00 GMT

In principle you are right, but it is about 330 jobs with 450 UWTs and 12200 mappings to be drawn manually.

The metadata browser and I are great friends, but the integration of UWTS in the job is really very complex . I think I will invest a few more hours in R&D 😁

Thanks again for your support