I'm not sure whether you try to directly upgrade the application from classic to EPMA through the architect, or you try to extract the .ads metadata from the classic application to load it to the EPMA. Though I have found this excerpt in the architect 188.8.131.52 readme, section known issues:
13688538 -- If you use the From HFM Files option to generate an .ads file, the resulting file may include an Alias property entry in the DimensionsAssociations section for the CellTextLabel dimension. It may also include an Alias column in the CellTextLabel dimension section. This is incorrect, because the CellTextLabel member class does not support the Alias property. If you try to import this generated .ads file into an existing Performance Management Architect Financial Management application, a validation error may occur.
Assuming that you're trying to load the extracted .ads file when you get the errors, you can try to modify the proper sections using an editor and excel as follows:
1. locate the DimensionAssociations section and find the line beginning with CellTextLabel and associating to Alias, then remove it
2. then locate the CellTextLabel dimension, copy-paste the content of the section to Excel, including the labels header, then use texttocolumns to convert this content to columnar format, remove the Alias column (including the heading) and reconstruct the delimited text for the remaining columns, then replace the CellTextLabel dimension section in your open editor.
3. Save the edited file and retry to load it to EPMA.
Thanks for the excerpt, this is handy. My issue was mainly related to using Architect feature to upgrade from classic to EPMA.
I ended up resolving the issue my creating ADS file from Classic , then creating EPMA Shell and reloading , dimensions , grids , forms data , security etc.
Just to provide some background it could have been our application only as i didn't see any issue converting classic to EPMA using sample application,
Our application was built in EPMA and was working fine but issue was related to CalcManager not validating accounts dimensions.
hence i had to convert EPMA -> Classic -> EPMA back to resolve this issue.
We are using EPM 184.108.40.206.104 Patch as an FYI.