Ok, I have never used the Salesforce connector. But I do think we can take steps to get your Filter Query working. I would do that by checking the outputs of the data and checking the column names.
So currently this is your flow:
- Trigger - When a Record is Modified
- Filter Query - Local_Sales_Manager__c eq 'PersonName'
- Get Records - Opportunities
- Get Records - Oracle Quotes
I would add a compose step to the flow after the initial trigger, and put the dynamic content from the trigger (Opportunities) into the compose step.
So you should have:
- Trigger - When a Record is Modified
- Filter Query - Local_Sales_Manager__c eq 'PersonName'
- Compose
- Put the Opportunities Dynamic Content from the trigger in this compose.
- Get Records - Opportunities
- Get Records - Oracle Quotes
Then run the flow.
When you look at the results of the flow you are looking for 2 things.
First: Look at the result of the Compose. This will show you what the output of that Opportunities looks like. So you will know if it is a string, number, and whatever is being pulled for that data.
Second: Look at the outputs of the two Get Records. You want to see the specific column names as well as the data that is returned. The specific column name should show you how to type the name in the Filter Query of the Get Records.
So if the output of Get Records: Opportunities shows the column as "cafsl_Opportunity_c": "OP1234" then you can copy and paste the column name cafsl_Opportunity_c and then put that into the Filter Query of Get Records: Opportunities. You also know that the data itself is a string.
However, if the output shows "cafsl_Opportunity_c": 1234 then you know the type of data is an integer and you would not use the single quotes ' around your dynamic content in the Filter Query.
Do you think you can try that or something along those lines? We are basically trying to get the Filter Query for the Get Records: Opportunities to work correctly. And to do that we have to run tests to see what the data is supposed to look like.