12-16-2021 01:47 PM
Cultures have been enabled in my current client application to accommodate non-English member descriptions. The Metadata Builder template downloaded from Marketplace does not accommodate columns to import the culture and foreign language descriptions. Does anyone have suggestions on how to load these properties?
Solved! Go to Solution.
12-16-2021 01:47 PM - edited 12-16-2021 01:48 PM
Hi Rochelle!
If you have the culture in excel you could create an XML from there to update only the field with the culture you want to change. (See example below)
Do not forget to change the dim type, the name of the account and the culture codes with descriptions.
Be carefull not to have a too long description. (max 200 characters i think)
Hope that helps
Nic
<?xml version="1.0" encoding="utf-8"?> <OneStreamXF version="6.3.1.12121"> <metadataRoot> <dimensions> <dimension type="Account" name="CorpAccounts"> <properties /> <members> <member name="CurRatio" description="Current Ratio default" > <descriptions> <description culture="en-US" description="Current Ratio EN" /> <description culture="fr-FR" description="Current Ratio FRFR" /> </descriptions> </member> </members> <relationships /> </dimension> </dimensions> </metadataRoot> </OneStreamXF>
12-16-2021 01:47 PM - edited 12-16-2021 01:48 PM
Hi Rochelle!
If you have the culture in excel you could create an XML from there to update only the field with the culture you want to change. (See example below)
Do not forget to change the dim type, the name of the account and the culture codes with descriptions.
Be carefull not to have a too long description. (max 200 characters i think)
Hope that helps
Nic
<?xml version="1.0" encoding="utf-8"?> <OneStreamXF version="6.3.1.12121"> <metadataRoot> <dimensions> <dimension type="Account" name="CorpAccounts"> <properties /> <members> <member name="CurRatio" description="Current Ratio default" > <descriptions> <description culture="en-US" description="Current Ratio EN" /> <description culture="fr-FR" description="Current Ratio FRFR" /> </descriptions> </member> </members> <relationships /> </dimension> </dimensions> </metadataRoot> </OneStreamXF>
12-16-2021 01:49 PM
Thanks for your reply Nicolas.
12-16-2021 01:48 PM
MindStream MetaData Manager | MindStream Analytics already does the XML creation based on cultures available.
12-16-2021 02:19 PM
Shameless plug - OneStream - Importing Non-Default Descriptions - Perficient Blogs
01-14-2022 05:12 PM
This was a good blog! Very helpful. I see how you can switch the culture for an individual which is really cool. I was wondering how to display both english and french - specifically in a metadata report that shows the member and it's properties. I just want to show the french description property on that metadata report only.
01-14-2022 05:07 PM
I have a related question. Once we have alternate culture descriptions setup, is there a way to call a specific languages description in code? We have a report where I'd like to display both the default English description and the French Description of all our members.
I have a UD8 Description member that is a DynamicCalc to pull description on the report:
Dim UD1Desc As String = api.Pov.UD1.Description
Return UD1Desc
I'm looking for an equivalent for the French language item. I found this but not sure how this could apply to get the French description: api.SI.Culture.Equals("fr-FR")
01-14-2022 06:07 PM
It is not a description. If you use member info, you should see something like Descriptions. I think that is a dictionary. Not in front of a system now.
07-13-2022 02:32 AM
Hi all
Can someone let me know how this is enabled under a Cloud Hosted application?
We have the codes - I think, but when we select one or the other * Spanish and / or Eng - US - we only see data display as Eng-US. The Spanish one is not affecting data display.
Thank you for your tips.
Nouria
02-12-2023 02:45 PM
We are cloud hosted. A setting had to be updated on the servers, but once the setting was updated for any cultures you want to use (we created some fake ones for extra descriptions of metadata like Disabled Date and Purpose or Owner), then you have access to them in the system everywhere. We do not turn on cultures, but we do populate these extra fields with alternate information about our metadata.
I later learned the code to setup the UD8 member to display cultures in a Metadata cube view. We use this in our UD8 members and then pull them into the report with the Annotation View member:
'Get DimensionID
Dim udDimpk As DimPk = brapi.Finance.Dim.GetDimPk(si, "Corp_CostCenter")
'Get Member ID
Dim iMbrID As Integer = BRApi.Finance.Members.GetMemberId(si, DimType.Ud1.Id, api.Pov.Ud1.Name)
'Create list of descriptions
Dim objList As List(Of MemberDescription) = brapi.Finance.Members.ReadMemberDescriptionsNoCache(si, udDimpk.DimTypeId, iMbrID)
'Loop through listing
For Each mMbr As MemberDescription In objList
If mMbr.MemberDescriptionPk.Language = "fr-FR" Then
'return only French description
Return mMbr.Description
Exit For
End If
Next
02-12-2023 02:48 PM - edited 02-12-2023 02:49 PM
My new question is if we have any kind of xfmemberproperty query for the cultures in Excel Add in or Spreadsheet tools. I really need to be able to query these values in excel to support what we added into our XML metadata builder. If we update existing metadata we want to query these values to make sure we don't lose them.