I hit a weird problem that is new to this project I'm working on. Up until a week ago this kind of thing worked fine.
These are lookup tables that sometimes don't have any records associated with the parent table.
Here, ClientPartner isn't always populated because the client might not have a partner. This worked fine up until recently:
Set(
UserItems,
Filter('Fitness Clients','Created By'.'Primary Email' = UserEmail || ClientPartner.Mail = UserEmail)
);
Now, the filter returns nothing in the case of the ClientPartner being Blank even though there are several records with the 'Created By' matching the UserEmail. Imagine no ClientPartners at all and getting nothing even though there are plenty of records created with the email address UserEmail. It is like "OR" no longer does anything. Now I have to use this, which of course has delegation issues and warnings about large datasets showing up now:
Set(
UserItems,
Filter(
'Fitness Clients',
'Created By'.'Primary Email' = UserEmail || (!IsBlank(ClientPartner) && ClientPartner.Mail = UserEmail)
)
);
Here is another example that now fails when the 'ClientCredits' lookup is empty...

Report
All responses (
Answers (