Hello,
We would like to produce an XML or XLS file with the documentation present in our presentation layer of our semantic model.
How can we achieve this please ?
Regards.
Jean-Pierre
Hi Jean-Pierre,
One solution could be exporting and downloading the semantic model to RPD file following these steps:
Export a Semantic Model:
Download an Exported .rpd File:
Then you can open the RPD file on offline mode using the Admin Tool.
Go to Tools -> Utilities... -> Generate Metadata Dictionary. It will generate the metadata in XML format.
Also, you could also export to zip file, which will generate files in JSON format inside. Then you could use Python to handle the JSON fiels.
Regards,
Ezequiel.
Hi @Cindy Owings-Hutchison It sounds like you are proposing an Idea Lab request (enhancement). Please check this one.
If it is what you are seeking, please up-vote and comment the Idea. If not, please file a new one. Since this is a discussion, and not an Idea, your request may be overlooked here.
Hi @Jean-Pierre Hoedenaeken ,
It's not possible to produce the Repository Documentation directly from the Semantic Modeler. You have to export it as RPD file and use the Admin tool.
Yes, its not included in the Semantic Modeler , you need to follow the standard process using Admin tool only.
Arjun
@Pravin Janardanam-Oracle - can comment on any public roadmap plans for metadata dictionary.
Access to the semantic model presentation layer metadata should be on the roadmap for this product. Users sharing data that is extracted from these tools often want to include the dictionary of descriptions and having it available would ease their burden.
Yes! This would be so helpful to those of us who support large organizations and have a lot of models to support. It would also help us keep our data dictionaries up to date or at least related to the data in analytics.
@Cindy Owings-Hutchison , while probably not what you look for as you expect (rightfully) the tool to cover the need, the json format of the semantic model is simple enough to easily generate any kind of documentation you need with a simple script. The older MDS XML format had tons of IDs and UIDs and also some FQDN defining relationships between objects, and had a number of extra layers in the code, the new json is a lot more straightforward.
Description: The Oracle Fusion Data Intelligence (FDI) Product Roadmap Update provides an overview of the latest developments and future plans for FDI. Oracle Product Management experts will share upcoming capabilities, key enhancements, and product direction, helping attendees understand what is changing and how these…
Hi! I am looking for audit logging for Analytics objects, such as users creating, modifying, or deleting datasets, dataflows, schedules, etc. The traditional Presentation Services component provides such logging in domains/oas/servers/obips1/logs/auditjson.log, which contains audit information for catalog objects,…
I'm trying to index a Local Subject Area so I can use it in my AI Agent, however, I keep receiving the generic error below. Request status(500) : error = {"prefix":"DSS","code":50000,"message":"There was an unexpected error while processing this request. Please try again."}
it is observed that in OAC while using case statements the output is not expected.For example if we have a case statment like case when table1.column1=table2.column1 then 'yes' else 'No' end as Attribute1 Now if i use this attribute with a fact-amount column attribute 1|| Amount on a report then we dont get the aggregation…
Once I select that value from the list box Region I created, I want to filter the table by my selection. See the images
