Do I have to build a separate flow to accomplish the same function across layouts in the same module?
I hate to constantly make comparisons to Zapier, but Flow's Zoho CRM triggers just don't supply the same level of detail and make it very difficult to perform simple actions. I end up having to make myriad webooks to make basic record updates.
Example: I have a custom module with 2 layouts. I have a trigger in Flow that fires when a record in that module is created or updated, but I can't update that same record without knowing which layout. So if I want to update the same record in the same module, I have to choose a layout I have no way of knowing, since there are 2 possible. Why not at least require the layout at the trigger level if I'm just going to need it later? There's also no way to filter by layout and no way to dynamically supply the layout ID even if it was supplied!
I realize a lot of this can be solved by knowing Deluge or how to write custom functions or knowing the syntax of all Zoho's variables and keys and terms (such as they are), but that kind of defeats the purpose of "no-code" and even "low-code" applications.
Am I missing something obvious or is it just way harder than it needs to be? Why is the data supplied by the trigger so much more complete and flexible in Zapier?
Zoho Desk Resources
-
Desk Community Learning Series
-
-
-
-
-
-
-
-
-
Zoho CRM Plus Resources
Zoho Books Resources
Zoho Subscriptions Resources
Zoho Projects Resources
Zoho Sprints Resources
Zoho Orchestly Resources
Zoho Creator Resources
Zoho WorkDrive Resources
Zoho Campaigns Resources
Zoho CRM Resources
Writer Get Started. Write Away!
Writer is a powerful online word processor, designed for collaborative work.