Open coletaylor1 opened 7 months ago
to reiterate: the issue here is that we should have caught this at compile time in Check() and never gotten to the point of having a runtime exception. I'm guessing it's an expression like Set(Accounts, Accounts)
We log the below expression and then see an InvalidOperationException thrown. The card does have two Dataverse tables attach so I suspect they try to assign these to variables. Still, we set a flag to not break this at runtime and if it's a user error, I believe check should fail right or a proper exception should be thrown.