Hello everybody,
I am using Dynamics 365 fOps 1611 Release (Dynamics AX7) locally and in the cloud and I have got some issues with the import/export-framework regarding security metadata customizations. Locally for creating and exporting the security metadata, and the cloud for importing the metadata.I hope, someone can help me.
1) I am not able to export the security privilege metadata customizations entity locally, but the security role metadata customizations entity and the security privilege metadata customizations entity can be exported. The following picture shows the failure :

When I try to download the package of this entity, the following error message is thrown:

I do not know, where to find that InnerException. The only solution I have found was to change the endpoint address from [...]localhost[...] to our real IP adress within the web config, but there was no endpoint address in there. The only config data in which I found the endpoint address was 'Microsoft.Dynamics.AX.Framework.Tools.DMF.ServiceProxy.dll', but changing the endpoint address there from localhost to our IP even got it worse. After that and before correcting back to standard, I was not able to export any of the security metadata customization enitites. Is there a way to fix the privilege metadata customizations entity export?
2) The import of roles and duties also does not work properly. It does not matter, if it is imported as a package or both as an Excel-file on their own. It does not matter either, if it is imported locally or to the cloud. When I try to import the security role metadata customizations entity or the security duty metadata customizations entity, I get the following error message, depending on which one is imported:

The only solution to solve this problem seems to be customizing the fields of the entities from 'Allow Edit - No' / 'Allow Edit on Create - No' to 'Allow Edit - Yes' / 'Allow Edit on Create - Yes' within the AOT via Visual Studio. But this also means that I have to customize the 'Application Foundation'-package. Is this the only way to solve this problem, or are there other possibilities to make these imports work?
I would also appreciate if I got the information that these problems are caught by a bug or by functions which are not built in completely yet.
Thanks for your help.
Christian