Dataverse Trigger Errors

[esang]

I have a flow that has been working on it's own for at least a month but last Friday it started to change the trigger when it is saved. I have tried rebuilding the flow on my own and other's have as well and we all get the same errors.

My trigger is when a row is added, but when I save the flow and go back to it to make sure my changes are there the trigger is changed to user or replace and the scope is user instead of organization. 

Weirdly enough I also get different options for the trigger when this happens as well. Me and the other users who have tried to fix the flow all have admin access in the environment so that couldn't be an issue.

I only want the flow to trigger when a row is added because even if I leave the trigger to when a row is added or deleted the scope changes to user as well instead of keeping it at organization.

[wskinnermctc]

Is there a difference between having Admin access and what the individual Table Permissions are set as for different security groups?

Table Permissions

Like if you go into the Table Permissions and add yourself as an Owner, or a Member of the group and then check the permissions settings to all, does it change how the trigger responds?

I don't know if Admin access means you have the ability to change things, but it doesn't really recognize you as part of the group permissions for the individual table?  

[esang]

When I changed the connection to dataverse to another user it said that the user's connection just has to have at least read access to the table in order to use the trigger.

[wskinnermctc]

In the table Properties what is the setting for Record Ownership?

Is the box checked for Rows in this table Have an access team?

[esang]

The record ownership is user or team but I feel that the access to the table isn't this issue but the trigger itself, it was working for at least a month without problems but last Friday the settings for the trigger changed on its own and keep going back to it

[wskinnermctc]

Maybe you're right. I don't know how to fix a trigger so I'd basically troubleshoot anything I can change.

What about the Data > Connections?

Could you create a new one and try it with the new connection?

(Just looked at mine and literally realized that it wasn't connected, needed to be fixed, in this environment because I changed my password. The other environment connection is fine.)

[esang]

Thanks for the suggestions- When this problem occurred there was an additional connector to dataverse through my account (so there were 2 identical connectors on the trigger) even after adding 2 other account's connections it still presented the problem.

I will still try again to disconnect and readd my connection but I still don't understand why it would change the trigger like it has been doing.

[esang]

It is still doing the same thing after breaking and the readding the connector. 

I just need the flow to save as when a row is added but when I save it as that and then go back in to make sure my changes were saved it changes to user or replace for the change type.

I don't know if this makes a difference but when the flow was working the change type in the run history said 1 but now it says 5 if it works (for when a row is added)