![]() Here are some basic rules of thumb when migrating permissions using Workbench or any other tool:ġ. ![]() ![]() However, you can access the MdAPI directly with the Workbench tool, which helps to eliminate much of the mystery. The bad news is that they can hide the MdAPI implementation. The good news is that they typically handle the creation of any necessary MdAPI elements so you don't have to worry about missing an XML element or a metadata entry. There is some good and some bad news when working with any of the client apps that are built on top of the MdAPI. And regardless of how it happened, you're left confused and with the time-consuming task of manually configuring permissions or settings in your target organization. Our documentation explains what is and isn't supported in the MdAPI, but it doesn't account for what happens when you try migrating permissions and settings. When working with profiles and permission sets in the Metadata API (MdAPI) have you ever wondered why a permission didn't migrate as expected? Maybe this happened when you were using a client app built on top of the MdAPI-like the IDE, Migration Tool, or Change Sets-instead of using the MdAPI directly, but regardless, you thought the permission would be there in the target organization and it wasn't.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |