Notifications
Announcements
No record found.
Adding custom 3D shapes to the Library 3D toolkit is excellent for quick access!This custom green arrow was accidentally put in symbols collection and can't be moved?Can't move it to Arrows collection because a lock icon prevents editing the field. The "Add Existing 3D Object" function was used to put the custom green arrow in Symbols collection.But using the same function won't work to add the custom green arrow to the Arrows collection.
It gives an arrow about an existing parent and no option to override.Is there a function to remove an existing parent?Is it possible to keep the object and remove or change the parent?Deleting it will damage all the guides the custom arrow is placed in.Thanks for any advice or support!
Hi smile,
The padlock means that the field in the Guides Model Driven App user interface is locked and cannot be edited.This doesn't mean that the data itself is not editable, maybe you can update this field through the Dataverse API, or Power Automate in the Dataverse directly.
If you can access Power Apps, you can edit the 'Collection ID' column directly:
Test Result:
Before:
After:
Thank you for your advice to edit the field directly in the Dataverse table which was successful, and now the Arrow 3D object is in the Arrow folder. Leah - your answer has been marked as verified as per your request.However, as a follow-on question related to improving the 3DToolkit Collections workflow for users, do you know how an admin can edit the managed non-customizable form to remove the lock from the Collection field entirely from the Model Driven App? It would be much faster for users to edit 3D Toolkit Collection fields from the Object Schema as part of the normal web workflow instead of going to the Dataverse tables each time this action needs performed.
Edit mode for the Model Driven App depicts a toggle checkbox for the Read-Only property, but after unchecking, the save button is not selectable at the top of the form. The warning at the top of the form does not indicate how to make an entire Model Driven App unmanaged so that it can be customized. The warning seems to indicate it's possible to create a customized form - do you know how?
Confusingly, in the same Model Driven App, it's properties for the icon are editable and savable. It is unclear why the properties of individual forms and their properties within the app are not editable and savable. Thank you in advance for any additional information you can provide for further customization! Here is the example saved change to the form's hosting Model Driven App which show a before and after saved modification to the app's icon. Note that the Apply button functions as expected after making changes to these properties. Note the saved status and ability to publish, which worked as expected and fixed the default Icon so that now the Model Driven App shows the proper Guides icon for all users. After these changes are saved and published, the proper Guides icon appears as expected throughout the rest of the Power Platform. This icon change indicates it is possible to save edits to the Model Driven App, but why edits cannot be made to form properties within the Model Driven App remains unclear?Thank you for any additional insights, Leah (and / or anyone else monitoring this forum) !
Yes, the form cannot be edit, which is by -design.
Maybe you need create a support ticket for Microsoft support team to get more details:
Get Help + Support - Dynamics | Microsoft Docs
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tom_Gioielli 55 Super User 2025 Season 2
Daniyal Khaleel 27 Most Valuable Professional
Soundari 15