...
| Code Block |
|---|
sfdx force:source:push |
Debugging Issues
And I get the dreaded message <unknown> duplicates value on record with id: <unknown>. This is where the time sink starts. How does a company the size of Salesforce allow an error of that level of bullshit even get out. It’s even worse than a Gack!
...
So I delete that one flow.
Nope.
Delete all but the main flow.
Nope.
But I’m starting to get somewhere now.
Flow Issues
So it seems that the new features in Winter '20 in Flows, where you do not have to manually create all the variables (great feature) is having an issue with the metadata. This Post states that it was confirmed by support. I can not see it in Known Issues though. But it seems to be the cause of the duplicate values issue also. See I had 3 Get Records lookups, all getting the same field value and because it could not understand the metadata of the {!Property from Get_VicRates.Levy_Rate__c} syntax it could not determine that {!Property from Get_NSWRates.Levy_Rate__c} was a completely different field.
Now, the thing is, I am trying to demo Spring ‘20 features, that rely on these Winter '20 features! I don’t want old fashioned Flows in my new Spring '20 flows demo. I now have to rebuild my flows to be compatible with Summer '19 so I can deploy them to a scratch org. Annoying.
(There is probably something more deeply involved than this, and probably a way I could do something if I sat here for another 6 hours and googled, but it’s a way forward for now, so I have to take it).
Weird Things
The end goal for me would be to create a scratch org that I am happy using that has all my standard modifications in it (eg as shown in New Salesforce Org).
...