Metadata management

If you are relatively new to OneStream, you should start with Application Import/Export of Metadata to extract and import Metadata.  Import/Export generates XML format flat files which you can edit in Notepad, or whatever tool you would like.

If you need to be making bigger changes (such as importing entire dimensions of members), then you might want to consider the OS Marketplace Excel tool that will generate XML from Excel sheets.  If you are handy in Excel, it is really easy to build your own Excel sheets to generate XML to match the metadata xml file format.

Be aware that when importing XML, you are adding/updating the metadata.  As in, you can't remove relationships or delete members via the out of box Import/Export.  This also means, it is pretty easy to import 10,000 members, but not quite so easy to get rid of those members if you imported them in error.

And finally, you can use the OneStream API via a Business Rule to surface anything you want from the dimension metadata, which you can output however you might like.  There are also OS API calls to create/update/delete metadata, which for adding basic members and relationships isn't too involved but can get to be a bit more work if you want to be updating some of the varying properties.  With the API. you can add/update/delete anything (within the same constraints as deleting via the normal user interface).

Somewhat along the lines of what you're asking, I'll describe an example of what is possible.  I have a OS Dashboard report that compares all the metadata (members and their properties along with relationships and all their properties) between two OS apps.  The report outputs what differs right down to a member or relationship property level.  if the two apps aren't in the same environment, I have a Data Management package that exports/imports all the metadata via a csv to a custom staging table so I can compare a remote app to a local app.  I went through Data Management package route rather then the out of boxed Import/Export via XML route so that the metadata can be brought over in a fully automated manner.  All this is pretty handy to figure out what has changed between Dev & Prod let's say.  All of this was done using the OS API.  What I am trying to get at is that when it comes to OS Metadata, you can do just about anything you want.