Hi Phil,
Onestream in the backend does not store any alphabetical value it only keeps number in the backend table for cube data.
What you can do is create a DBCL in that append all the intersection info and the annotation value to a dictionary and with that dictionary create a table in the backend and store that info there and when you want to access that information you can cache in that table as a dictionary and look for that value you want to refer using the intersection as key.
This will help you to store the information in bulk using a DBCL but to a custom table.
Hi Omkareshwar,
I'm not actually looking for anything custom. I'm talking about OneStream's standard annotation functionality (i.e. - V#Annotation). I want to populate the V#Annotation members in a data buffer in much the same way you would populate the numeric values in a data buffer.
Thanks,
How about a Form Import Template? There is a Marketplace solution (IMT - Import Template Forms) in which there are various Token driven forms such as this:
Then go to your Cube settings where you are looking to load this data:
Then create a data source to ensure Excel loads are enabled:
Or create an import template with tokens as shown in below screen shot and load through a base import workflow profile type
Search in Design and Reference guide for more on Tokens:
