15

There is a problem when importing customized workspaces into another users Dynamics 365FO system. Please see below for a detailed explanation. The problem occurs when you do the following: ____ 1 - Create a new workspace for user X. User X has no other customized workspaces. Therefore the control name for the newly created workspace is "usermyworkspace1" (if its the user's fifth workspace, it will have the control name "usermyworkspace5" and so forth, for now, its his first). 2 - Add your personalization to the workspace (i.e. tables/lists/links). 3 - Export the workspace as XML file. *** Please note that the exported file has the following name "User_MyWorkspace1Classic view", the same name/number as the control name of the created workspace in step 1. Lets say you want to import this customized workspace for another user, user Y. You have the option to do so by importing the XML file you created before. These are the following steps you would take: 4 - Create a new workspace for user Y. User Y already has two other customized workspaces therefore the workspace control name for the newly created workspace is "usermyworkspace3" 5 - Import the XML file (the file exported in step 3) 6 - You will receive a notification telling you to refresh the page to see the adjustments. However, after refreshing, you will not see any changes in "usermyworkspace3". Instead, you will find the adjustment in your first customized workspace ("usermyworkspace1") ____ We have found the issue for this error. The exported file (step3) contains the workspace control name "usermyworkspace1" and therefore can only be imported into another users "usermyworkspace1" and will not work in another (e.g "usermyworkspace3") workspace# than the exported workspace (step 3). This is highly inconvenient since users work in different departments, have different rights, etc. thus would never have the exact same workspace control name. Besides the fact that users never have the exact same workspace control name, at larger clients, it would mean you will have to do alot of manual work to get all customized workspaces up and running for the users. There is a workaround by changing the all workspace control name references in the XML file to the one of the importing user has. (notepad>edit>replace>replace all original workspace control names (e.g. usermyworkspace1") to the workspace control name of your created workspace (e.g. usermyworkspace3")). Please share/vote this idea! Thanks in advance Dillon Koense Dynamic People B.V. Microsoft Dynamics 365 Specialist

Category: User Experience
STATUS DETAILS
Completed
Ideas Administrator

The export and import of workspaces was recently improved as of 10.0.6 / Platform update 30. Importing is now based on the GUID assigned to the custom workspace on creation, so that it will not conflict with any existing workspace, even if there's already one with the same name. Additionally, importing the custom workspace will automatically add a corresponding tile to the dashboard.