Hey 
I found here GetA12 Login that the iconName in the form model should be automatically migrated. But when I use the migration tool it tells me:
“error”: “/content/subHeaderBox/majorButtons/button/0/buttonStyling Property iconName is not expected to be here”,
“path”: “/content/subHeaderBox/majorButtons/button/0/buttonStyling”
so I changed “iconName”: “label” to
"icon": {
"name": "label"
},
and every is working fine. but it is not automatically done in with the migration tool.
Best regards
Lara
Hey @lara-early-vale,
sorry for the delay within your request. The FE team is investigating your issue and gets back to you here
Best,
Nico
Hi,
I am not able to reproduce the issue with the latest migration tool (36.6.2 currently).
I can successfully migrate form models from version 35.0.0 to 36.6.2 (containing icons in various places).
For which version specifically did the error occur (meaning from which version did you start the migration and to which version did you migrate)?
Hey @lara-early-vale,
could you please give us a short update if your issue is still valid?
Thanks!
hey,
yes this is still valid. I dont know the version because ther is no “A12” version version. just a lot of package version. so I list them here. pefore the update the versions where:
“com.mgmtp.a12.base/base-model-api”: “26.3.0”,
“com.mgmtp.a12.client/client-core”: “13.1.1”,
“com.mgmtp.a12.dataservices/dataservices-access”: “35.0.0”,
“com.mgmtp.a12.devtools/devtools”: “5.0.1”,
“com.mgmtp.a12.devtools/eslint-config”: “0.5.0”,
“com.mgmtp.a12.devtools/prettier-config”: “0.4.0”,
“com.mgmtp.a12.expression/expression-core”: “0.2.0”,
“com.mgmtp.a12.formengine/formengine-core”: “35.0.0”,
“com.mgmtp.a12.kernel/kernel-core-runtime-api-ts”: “27.5.0”,
“com.mgmtp.a12.kernel/kernel-md-facade”: “27.5.0”,
“com.mgmtp.a12.overviewengine/overviewengine-core”: “35.0.0”,
“com.mgmtp.a12.uaa/uaa-authentication-client”: “6.1.0”,
“com.mgmtp.a12.utils/utils-connector”: “5.4.1”,
“com.mgmtp.a12.utils/utils-localization”: “5.4.1”,
“com.mgmtp.a12.utils/utils-localization-react”: “5.4.1”,
“com.mgmtp.a12.utils/utils-logging”: “5.4.1”,
“com.mgmtp.a12.widgets/widgets-core”: “35.0.0”,
For some places the migration worked. but not if I have the inconName in a button.
in our model we had something like this:
{
"type": "NAVIGATION",
"id": "button_5bac3",
"name": "Partner",
"buttonStyling": {
"label": {
"type": "Multilingual",
"multilingualText": {
"text": [
{
"locale": "en",
"text": "Partner"
}
]
}
},
"iconName": "label_important",
"priority": "SECONDARY"
},
"target": "screen-c1a2b",
"validation": "partial",
"scope": "ALWAYS"
},
and for this the migration failed
models were provided by project for further investigations
update: issue wasn’t reproducible on our side. seems to be an issue based on an outdated migration tool version
manual migration for this special case was successful