If I go to another app, say our task management app where that employee record is referenced using a lookup field in the form [Task] using the field [Employee_Assigned]. This throws a fatal execution error with no explanation:
test_Task = Task[Number == "00012"];
info test_Task.Employee_Assigned.Name;
Also if I try to get Name.first_name or Name.last_name, it returns [null] (which is not correct, the Name field has a value).
What is really interesting, it allows me to fetch other fields from [Employee_Assigned] as long as they are not name fields! Has anyone else had this issue fetching a Name?
I would assume the issue is due to the field type and you would have the same problem referencing an Address type field also.
In the Employees form in the other application you can add a formula field that points to the Name field, then try reference that formula field in the second app.
The other option is to create a function in the first application where you can pass the ID of the employee record to it and it would return the name, this could then be called from the second application.
I wrote a function that does this. The function has quite happily been returning the users name for the last ~three years. Yesterday, it stopped working and returned an execution error.
I spent several hours trying to work out what was happening and what, if anything, we might have done.
With your post, I am beginning to think it is a change from Zoho.
Damien, thanks for the response on workarounds. Yes I can confirm these workarounds work, I tested them yesterday before I posted here. I really don't like that option - Employee Name is quite literally the most commonly referenced field in Zoho creator for my company. I am working with Zoho support to try to fix this, it is surely some trivial bug introduced in the implicit "toString()" feature of the composite Name field.
Workarounds like formula fields and custom functions that just return a field value are awful when it comes to turning my deluge into spaghetti code that is incomprehensible. If it takes them more than a day to fix this I will have no choice but to do it, but I hate stuff like this.
Tim, thanks for the update. I didn't get an email from them, I had to implement a workaround which required me to update dozens of lines of code in 180 different workflows in Zoho, so I'm not trusting the Name field ever again!
So, three weeks ago, the scheduled reminder emails did not get sent because the script failed when getting the recipients name from a Name field (now fixed).
Checking the Logs, I can see the script failure.
Question: Any idea how to automatically inform people if there is an error from a Scheduled workflow?
Yeah I agree, when a workflow fails for any reason there should be an alert sent to developers. Zoho should have an option for this in the app settings, effectively a try-catch for the entire app. Using try catch on every workflow and function of every app is stupid and violates the DRY principle of coding. Unfortunately Zoho forces us to violate this principle a lot.
@support: It's been asked for many times, an email notification for a failure within an application, excluding "Validations" and "Successfully Executed Schedules". Is it on your radar? Thanks.
Reply to Alex RichA
/* */
12
Insert
Plain text
Rich Text
Add Comment
(Up to 20 MB )
Stats
3 followers
12 replies
111 views
Follow
Subscribe to receive notifications from this topic.