How to include Member IDs in data export
We are using an extender business rule to run FdxExecuteDataUnit and write the data (with dimensionality) to a file. The file generated seems to be a standard format with a column for each dimension...
Forum Discussion
Its strange that OS with their love of Guids, PKs, and Ids would only extract string names in FDX. I suspect its not a big ask for a feature to optionally include ID columns in the FDX library functions.
If you can wait a few more moments while your FDX is running, you could parse the result using a multi-threaded approach in an assembly or BR to add ID columns.
What is the use case for having the IDs in the resulting file? It could be that its better to derive IDs on consumption of the file instead of during construction. Just depends on where performance matters most.
RobbSalzmann the specific use case here is exporting data from OneStream to stage in ACDP and use in Power BI. Because Fdx only extracts stored data there is a need to apply the OS hierarchy to the data (which we already have an extract of). We felt the best way to marry the data with the hierarchy was through the member IDs in case anything would ever be renamed. We can not use the new Power BI connector because we are not Saas and our organization does not want to make the investment needed to get the connector. I figured the Fdx would be the quickest way to get the data. Additionally, it is easy to use the function to define the data needed. I am not great with buffers and writing code but I can probably piece something together by copying from existing rules we have.
I appreciate your feedback and will consider above. Feel free to share any other ideas you may have.
Thank you
Denise
