I’m guessing the Validate Data will not work if I’m trying to allow each tenant to have a unique instance of a value.
For example, each tenant will store their companies in the “Company” table. Each of them could have a Google, but I only want them to be able to add Google once. So there could be many Googles, but only one for each tenant.
I believe the Validate Data step would not work in this example, so should I use a condition instead or is there a simpler way to check?
Not sure it is any easier than conditions but you could also create a generated column in your table that combines the tenant with the value you are looking for (assuming that creates the uniqueness you need). That way you could stick with your validate action model.
That could work, but I would prefer to keep the tables clean. I guess I’ll go with conditions. It would be nice if you could combine fields in the Validate Data step.
That’s how it works in the daily business (we have to deal mit multi tenancy all day): canonical identifiers, like the (on table level-) unique ID as tenant identifier and your unique identifiers by tenant.
This also helps with reporting or any other access to the database outside your own code.