Yes you are corrrect.
But if i set
_accountmanagerlookuplogicalname_value eq null
in the filter
Wont that only work if the column is empty?
What about if the account manager changes from one value to another value?
then the flow wont be triggerd
EDIT:
Well i suppose i could set up another dataverse column named AccountManager_LastValue (string)
Then let the flow that updates the relationship column also put the AccountManager value in that column aswell.
Then i suppose it would work to have an filter expression
AccountManger ne AccountManger_LastValue
Would mean if a change in the sql table took place, then a new value wont match the "lastvalue" column and that would trigger the flow...
Am i correct?
If i am correct... i do not like this solution... i think it adds to much complexity to do this.