Dataverse: "When a row is selected" is now a legacy trigger?

[TomS2020]

Hi everyone,

I recently went into Power automate to set up a new Flow for my users. I was hoping to use the "When a row/record is selected" trigger but I can see it's now a legacy trigger.

It looks like for the time being I can still use it, but I'm concerned it will disappear down the line.

Can anyone shed any light as to why this has happened? Is there a better alternative to this trigger anyone can suggest? I'm not aware of any that do the same thing. Most of the time I use this trigger if I want to allow my users to run a Flow, in bulk against X number of records at once.

Many thanks

[AnthonyAmador · Accepted solution]

Hi @TomS2020 

You are right, the Microsoft Dataverse connector has been updated, for now you can continue to use the MS Dataverse (Legacy) connector with its functions, soon you will be able to use those functions in the new connector. 

You can find more information at the link , hope this helps. 

Cheers.

[timothym]

I have to say this continues to be my number one gripe about Flow/Powerapps/Dataverse/ or Whatever its new name is called when someone stumbles upon this post in the future. 

Connectors are continually deprecated, changed without warning (and changed back), etc. Because of this it makes it something very difficult to create important business processes when you have no line of sight on when something could randomly change / break a connector. This is a stark contrast to native workflows in Dynamics 365/CRM (which devs continually try to steer people away from towards Flows). Native WF's in dynamics can work for years without change, and the only possible thing that typically breaks them is understandably major dynamics updates but even that is rare to break native workflows.

Two months later and it still shows legacy and the "new" data verse connector still does not have this. So now as sys admins we are left with only one option to use the developers preferred route of business automation (flows): Develop an important business process on a legacy connector that implies it is deprecated and may stop without warning even in the immediate future.

[HerrMueller]

Seconded.

Also it is very confusing that built-in flow templates in Dynamics CE still direct to the legacy connector (like action cards templates in the sales assistant).. Currently it is inconsitent in many places.

[BinduRanjan]

Did you find any alternatives for this Issue. Very hesitant to use legacy connectors but not finding other option as well.

[PauliT]

Is there any news in this issue? I was just looking for update or replacement to old legacy "When a row is selected” but found none. We have been facing weird issues where trigger gets an entity id of previous entity, like it is getting value from browser cache. This could have serious issues in production environment because user has no way check which entity flow is using and data from.

[timothym]

Nope still using the legacy connector. Even MS Employee above Bindu had the same concerns lol. So not looking promising MS is actually on this..

[Eugene]

Haha It's very funny to see this issue as "Solved".

What exactly have you solved??? @AnthonyAmador 

I'll tell you more when you are trying to rebuild previously created Flows you can't use the new Dataverse connector. 
So the one way to use a new connector is to build a new Flow!

1. So in case if we have a bunch of processes we need to recreate them just because somebody decided to create a new connector from blank?
Is it legal at all?

@AnthonyAmador is it hard to convert json (of the flow) from one format to another to provide support for previous version?

[simonsnell]

Hi Anthony

I looked at the link you provided but I couldn't see any option to run a flow when an item is selected.  I want to select an Activity and run a simple flow which changes the Status reason from Closed to Open.

Thanks

Simon

[McMonty]

Hi,

Did anyone get anywhere with this question? From what I can tell, there is still no replacement for the Legacy trigger. Is it just a case of MS not pulling their finger out with a replacement?

[benema3000]

Same issue here, are there any updates?

[TomS2020]

Still no up-to-date replacement for the trigger.

However, although they have deprecated the old Dataverse set of tools, the "Select by record" is still okay to use until I believe August 2023 - by then I'd hope they've made a replacement.

[benema3000]

Is there an open user voice item? Or is there any way to track this progress. It seems quite crucial. Not to great to set up solutions for customers with deprecated triggers...

[jbarnandis]

Trigger "When a row is selected" is still a legacy trigger! Where is the updated one? · Community (p...

[ProfCranbberry]

"Hope this helps" is not a solution. The issue is still not solved and annoying. Such behavior is unprofessional.

[MCJ]

We are still waiting for a replacement for the trigger, it should be here before the Legacy Dataverse Connector stops working in October 2023.

I've not used this trigger since it was announcement of the new connector, as it was clear the other one would be deprecated. I've been using SmartButtons and webhooks to trigger flows for the last few years, details on my blog here.

PowerFx and Commanding does not currently support running flows, however, you could use them to launch a custom page and have the custom page (canvas app) run the flow, as a solution for now. It might take a little longer than using the OOTB trigger, but I think custom pages or SmartButtons are a better solution right now.

[InfinityRaine]

Agreed @timothym! Almost 2 years down the line as well! 

[marismourao]

Just passing by to say: It's August 2023 and nothing's changed

[djbryson]

It doesn't look like there's a replacement trigger, so you need to use "When an HTTP request is received" with a custom button.  The custom button can be configured with Ribbon WorkBench in XRMToolBox. 

[djbryson]

I should say, you can also use the new Command Designer in Power Apps for custom buttons.  You don't have to use Ribbon Workbench.