You’re offline. This is a read only version of the page.
50
Hi,
Just tried to import our DEV solution to UAT - it's a managed solution and this is version 18 so has happily imported before, in fact two days ago.
Now getting an error that relates to a Microsoft field/column in a Microsoft entity/table - both case entity and the Next SLA field are fully managed.
Error: 0x80044366 - Invalid name for attribute nextsla. Custom attribute names must start with a valid customization prefix. The prefix for a solution component should match the prefix that is specified for the publisher of the solution.
The schema name nextsla for type Attribute is invalid or missing.Custom attribute, entity, entitykey, option set and relationship names must start with a valid customization prefix.The prefix for a solution component should match the prefix that is specified for the publisher of the solution.
Even tried just adding this specific field to an unmanaged solution, and then importing it - import fails with same message.
I know apps recently got updated so could be related to that - so currently restoring UAT to another test environment - prior to last successful import of a solution, and before these updates. Will then reapply last working solution and follow up with an import of the currently broken solution. I may have to roll DEV back to same point and re-apply recent changes. Which were minimal - some view changes on case views.
Just wanting to do all the obvious stuff Microsoft support would ask for so if we need to contact them, we have as much data as possible.
|
App |
From |
To |
|
Agent Productivity Tools |
9.2.22074.1005 |
9.2.22082.1003 |
|
D365 Sales, Enterprise Edition App |
9.0.22074.10001 |
9.0.22082.10004 |
Thanks Leah - the Microsoft Patches weren't the cause - removing the active layer as you suggested solved it. Not sure I fully understand why that fixed it, but solution imported perfectly.
Thanks...
Hi Leah,
Thanks for the suggestions will give them a try.
Changing the solution XML, that's going back to my early on-prem CRM days. Yesterday evening I had similar thought and did try removing the fields XML from the Solution xml, and it imported perfectly despite the field having identical properties in target and source.
My concern is modifying XML on a client system so now I have taken the approach of roll back two days on DEV + UAT - re-apply customisations, then export and import solution regularly.
That is working, solutions importing to UAT so still suspect those two updates which I haven't applied this time. Should know in a few hours and will post an update.
Once I have the changes, I need in UAT and its gone live, I will re-test the two Microsoft patches on a test rig and see if that's what breaks things. I will also try your suggestions as an alternative to completely removing the field.
Thanks for your help,
Andrew
Hi A D Perkin,
Maybe you can try to use following ways to test again:
1.Remove active layer for the nextsla attribute.
2.In the two environments has different names in attribute and has different prefix hence suggested to change the same for two environments.
3.workaround:changing the isCustomField from 1 to 0
(1)Extract the solution zip file.
(2)Open customization.xml file and check for the attribute <nextsla> under < entity Name="incident">
(3)Just change the <IsCustomField> from "1" to "0"( IsCustomField>0</IsCustomField>) in attribute “nextsla” and then save the file and Zip the entire solution again
If none of the above options are available, you can open one ticket for Microsoft Support:
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,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (