First look at Power Fx command buttons for model-driven apps - Power Platform Unpacked #11
Vložit
- čas přidán 5. 07. 2024
- Join me for a first look at the new Power Fx command bar buttons in model-driven apps (preview) as we answer the question "Is this really the end of the Ribbon Workbench?!"
For a step-by-step guide on how to add low-code buttons to your model-driven apps check out 👉 www.develop1.net/public/post/...
00:00 Introduction
01:00 The Ribbon Workbench and low-code
01:45 Power Fx with modern commanding in model-driven apps
02:00 Brief history of the command bar
07:07 Demo of Power Fx in modern commanding
18:25 Running JavaScript from modern commanding
19:29 Is this the end of the Ribbon Workbench? - Jak na to + styl
Scott! it is a great walkthrough of Power Fx Command buttons. Definitely it will take some time to used to this , as we are more used your Ribbon workbench from many years.
Really appreciate all things you have done for the community Scott
Thanks for this Scott - really helpful stuff and well explained!
RWB will forever remain as a tool of our hearts and lives.
Must have been an emotional moment (in whatever way) !!
Great walkthrough, Scott, this is a step in the right direction for the platform!
Good news - Modern commanding is now out of Preview!! 👉 powerapps.microsoft.com/en-us/blog/announcing-the-general-availability-of-power-apps-modern-commanding/
Hope things are well Scott. Enjoyed this video. Thanks.
Freakin’ useful for those of us who have spent tons of hours in canvas apps and need to feel comfortable when working with model driven apps! Thank you for this, truly insightful!
Looks great Scott, great job working with the product group on this.
Well explained Scott!!! I have always loved the *RWB* !!!
This is amazing demo, very informative and authoritative demo for anyone who wants to learn how to use modern command designer and Power Fx based low code technology.
Cheers for this Scott. It's never the end with CRM but I can see RWB going from the 80:20 to the 20:80 and for simpler things I will now reach for PowerFx.
WoW, Scott. Thanks, very useful.
Hi ! Very good video, thank you Scott 👍👍💪💪👌👌
Thank you! Are you planning on using Power Fx command buttons for anything specific?
Awesome!
Excellent find!
Looking good. Hoping the ALM side of it all hangs together when it goes GA. Beard looking good too!
Very impressive.
Great stuff. I need to work on learn these fx commands.
Hi Scott, do you know if RWB and new command bar editor be used together? e.g. use command bar editor to add new button on contact form and then use RWB to edit existing OOB buttons on contact form?
Hi Manoji - the ribbon workbench and commanding V2 will be able to be used side-by-side at runtime- however they won’t be able to edit each other’s buttons. Eventually I expect there will be the ability to upgrade classic buttons to the new V2 buttons at which point they will not be editable in the ribbon workbench.
How to add buttons in the home page of customer service workspace, not in the dashboard. Want to add button next to save as, new, set as default and refresh all. I tried to use the ribbon workbench but the button is not visible.
They stole your IP… this is ribbon workbench 2.0… rwb lives on 🤙🏽
Hi Scott, how can we get the current user email, I want to add a visibility formula where CurrentUser.Email = Self.Selected.Sponsor (where Sponsor is a calculated column). But the thing is User().Email it`s not working, is there any other way?
Hello, I have to create a button with a boolean option behind. The Button should start a power automate function. So: yes -> start power automate, no-> don't start power automate. Could you pls help me?
Pain is that if i have two fuctionalities in development with PowerFX buttons. I.e. for Opportunity and second for Account.
I want to move Opp to Prod, i will add MD app to solution and it will require to add Account, and will bring Account buttons on prod, though i dont want to.
As always, great content! I'm not sure if you've run up against this, but we're utilizing a Model-driven app created by an ISV but when we go to edit the command bar the component library is auto-created with the generic default environment publisher. Do you know if there is a way to create the component outside of that ISV's Model-driven app utilizing the publisher our company uses? Or, are we just stuck having a solution with the messy "cr9843_defaultcomponentlibrary" as the component name?
Thanks for all you do, Scott!
Hi! Thank you and thanks for watching 😊 Could you try adding the ISV App to a custom solution that uses publisher with your custom prefix - then edit the app and add the command from there?
@@ScottDurow Thank you for the reply! I tried that and the same thing happened. It force-creates the component library even in our custom solution. Maybe just one of those growing pains on the new functionality?
The visible fx is not working for me. I am using Self.SelectionMax=1 .But still, the button always shows when no record is selected on the main grid. Even if I set the Visible to false it still shows
Thanks Scott, these videos are amazing!
I @ed you for some assistance on this but the character limit is limiting, my apologies, went blog, twitter youtube on my journey...
Felt I could explain it better in a few more chars...
[Update] Use a visibility rule similar to :
'My custom table (Forms)'.'My custom form'=true
Tested this (With my form and table names!!) on both Sub-grid and Main form level commands both are yielding the error;
Incompatible types for comparison. These types can't be compared: NamedValue, Boolean
I'm at an absolute loss, I don't see to be able to define the form as anything other than the NamedValue, and that form being active should be the logical test...
Hi! Thank you for watching ☺️Yes, you are right there does seem to be something wrong with a recent update - I am looking into it for you and I’ll keep you posted!
So now we created lets say custom ribbon solution, added existing model driven app to it and made changes. If someone added new entity directly to the model driven app, will those will be available in our existing custom ribbon solution?
The new commanding is linked to a model-driven app. You must add the commands to the solution that contains that app. If you add a new entity to that solution, any commands added to a different model-driven app solution will not available - you will need to copy/paste them from the other app.
Any experience using Ribbon Workbench in combination with Power Fx command buttons? More specifically, any issues?
I am finding that when I publish from Ribbon Workbench, for some reason, two sub-components from another solution are getting added into the ribbon 'minimal solution': the model-driven app using the entities, and the Canvas component holding custom commands I already. Then, I cannot open the ribbon solution again in Ribbon Workbench. I've managed to get around this by repeatedly removing those added components from the ribbon solution, but feeling like I'm standing on shaky ground...
Hi Len - there is a bug currently in the new commanding - it will be fixed soon so you will be able to use it without this issue in combination with the RWB!
@@ScottDurow Thanks, Scott!
@@ScottDurow Until they fix that, are there any pitfalls to be aware of? Should I just keep removing the extra sub-components from the 'ribbon-only' solution?
Apologies if this is documented somewhere. If you have a link, I'll read up myself.
@@lencardinal1584 Yes - that's it - just keep a clean Ribbon solution for the RWB. Other than that, the RWB and new Commanding work together well.
How do we launch a Flow from the Formula bar, so that when a button is pressed, a specific flow is launched? And how do you debug this?
Hi! That's not currently possible from a Power Fx expression - but you could show a custom page and then run the flow from there - develop1.net/public/post/2021/08/14/OpenDialog-SmartButton-Commandingv2
@@ScottDurow Oh wow. You are very prompt! Thank you. I've been searching for how to do this for hours!
@@ScottDurow How do we debug the scripts for these?
Hi Scott,Are you also one of the makers in Power-Fx?
How do I access current form mode to show / hide button ?
There is a Self.Selected.Unsaved flag that you may be able to use depending on your use case.
Facing weird behavior, If I add a button on the Order form ribbon while editing app ABC then the same button is not appearing in app XYZ. As par my understanding, ribbon will be available for only that app and will not reflect in other apps.
Hi Mohsin - you are correct - currently the buttons will only be available to the app you add them to.
Anyone? so there is no way to hide legacy buttons using power FX? Will power FX ever support legacy buttons?
Hi Darin - thanks for watching 😊 Currently you have to use the Ribbon Workbench to hide legacy classic buttons. I do hope that classic commands will be be moved to modern commands so that they can be edited in the modern editor!