Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
With 7.3 PU12, every time I am trying to import a personalization containing only a user-created workspace, I have this error : "The imported document contains one or more personalized lists or tiles that failed security validation and cannot be used in this workspace. The list(s) that failed validation has been removed from your workspace."As a result, I have an empty workspace created.Both users (the one doing export and the one importing) are SysAdmin.Am I missing a step ? Did anyone manage to do that?
Is this an out of the box workspace or one you created. It implies that the workspace has some feature you are updating that are not allowed for a lower level role that has access to it
this is a user-created workspace (created from scratch) and both users are sysadmin...
Bringing this topic back up again, we could really use an answer for this issue :). Thanks.
Same - only post I could find with a similar issue.
My findings so far : If you modify filters on the form using options > advanced filter/sort, and push the form to a workspace, if you try to export it to another user, it will fail security validation. We have raised a bug to MS. As a workaround we catered for filtering directly in the code, which seems to work correctly.
Please note that the workspace is a snapshot of a user's UI, therefore his filters will be exported as is. E.g, if you use the return value of a function like groupsForUser() in a data range through code like this :
SysQuery::valueEmptyString() + ',' + UserGroupList::groupsForUser()
, it will export the filter with the groups corresponding to the user who created the workspace. E.g : If user A creates a workspace with filters on his user group, when he exports to user B, user B will still get the filters corresponding to user B. Therefore, for dynamic queries, we coded methods with the QueryRangeFunctionAttribute attribute in a custom class
public static str NESBlockUserGroupId()
return SysQuery::valueEmptyString() + ',' + UserGroupList::groupsForUser();
Then added to a range as follows in the code :
This is the only workaround we've found, and we've spend quite some time on it.
P.S : Don't bother debugging the XML file generated for workspace import, its useless and most of it is in beautiful hexadecimal code :)
Hi, can you provide feedback from MS to the bug you raised? Seem like this is still unsolved issue, I have the same issue currently.
Hi Frantisek, I did not bother following up with MS regarding this issue and ended up archiving the case. If you provide some details maybe I can help. But my advice is : Do not use this feature, it is severely broken and inconsistent. Bad development at its best.
Did you looked at these already discussed threads ?
Looks like some of your users are not having proper access to use the personalization you did. Like you have created a tile using list page but one of the users doesn't have an access to list page or the table which contains the data of that list page.
Yes I did. First link is link to thread where there is used user ID related filtering, which is not my case. The second link is link to this thread itself.
No, access rights is not the issue. It really seems that it has somenthing to do with using of personally defined joins in Advanced filter/sort as mentioned Ashwin Jugurnauth.
Up to know I did not find anything reasonable explaining the issue.
Business Applications communities