75,730
*This post is locked for comments
I left a comment on this link as it appears that whatever this bug was it has not been fixed.
I have found that an & within the last few characters of the maximum defined field length acts up when passing through an xml translation because & may get expanded to & and then the code may truncate the string to the defined length before converting back, chopping off part of '&' and throwing an error. I make a pass and substitute a '-'.
Nick, it does not appear to like the ampersand '&'
Are you referring to the account category descriptions which can be selected in the "Link to Dimensions" column (column J)? If yes, I am unaware of any character limitations as my current client uses account category descriptions with ( , () \ /) type values.
I apologize if I misinterpreted your question.
By the way, I just noticed also that MR 2012 does not like special characters in the category descriptions. Is there a list of what characters it accepts?
Hi Richard,
You are correct in that "Account Types" used in row formats will NOT migrate over to MR 2012. I ran into this issue during my last FRx to MR migration and ended up having to reconfigure the row format (without account types) prior to running the migration process. Sorry to confirm the bad news. Hope the remainder of the migration goes well.
Nick
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (