-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RWB does not work once you added Command Definitions #94
Comments
Hi Johannes,
Hope all is well.
I have discussed this with the product team and it has been identified as a bug in the new commanding feature. It will be fixed in version 9.1.0.14 of the App action solution.
Thanks,
Scott
From: Johannes Mueller ***@***.***>
Sent: 22 March 2022 02:37
To: scottdurow/RibbonWorkbench ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [scottdurow/RibbonWorkbench] RWB does not work once you added Command Definitions (Issue #94)
Hi Scott,
as already discusses on Twitter, I will file an issue here as well.
Following scenario: We added new command definitions to an entity. We also got existing custom ribbons for this entity in place there already.
Now if we want to edit those ribbons, RWB tells us that the solution contains non-entity components, because the command definition (component type Canvas App) is also added automatically to the solution, once we add the entity to the temporary solution.
Even manual removal of this command definition app does not have any effect. The message is still shown.
Tried both, in modern as well in legacy solution management.
Maybe you can extend the validation of solution components to accepting component type canvas app?
-
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fscottdurow%2FRibbonWorkbench%2Fissues%2F94&data=04%7C01%7C%7C6fec55c125b44af6137308da0be78036%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637835386153488592%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=2Mis4H2ev%2FvhwF8kX8vI8VMCr38A4g3lzFpAzXjvSDE%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAV46UMHLAPABHZWBHBWE7DVBGIDLANCNFSM5RKI544A&data=04%7C01%7C%7C6fec55c125b44af6137308da0be78036%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637835386153488592%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=q07zRrZL7HGxKDShcLC4%2BwmNxuB7xtYLPg0V3wQirHw%3D&reserved=0>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Scott,
as already discussed on Twitter, I will file an issue here as well.
Following scenario: We added new command definitions to an entity. We also got existing custom ribbons for this entity in place there already.
Now if we want to edit those ribbons, RWB tells us that the solution contains non-entity components, because the command definition (component type Component Library) is also added automatically to the solution, once we add the entity to the temporary solution.
Even manual removal of this command definition app does not have any effect. The message is still shown.
Tried both, in modern as well in legacy solution management.
Maybe you can extend the validation of solution components to accepting component type "Component Library"?
The text was updated successfully, but these errors were encountered: