Quentin CHURET
09/16/2024, 2:15 PMCeligo AI
09/16/2024, 2:15 PMAI generated answer (using internal Slack threads):****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ****** In NetSuite, the "After Field Edit" trigger is a client-side trigger and it won't work with scheduled workflows. Scheduled workflows only work with server-side triggers because the record never enters the client. Therefore, you can't trigger client-side actions like "Before Edit" or "After Edit". You should stick to "Entry", "Exit", and possibly "After Record Submit" for scheduled workflows whenever possible. If you're trying to trigger an "After Field Edit" action from a list view, it's important to note that this might not work as expected. The list view won't fire off client workflows. However, a "Before Submit" action might work. To test this, you can add a single action to show a message after field edit and see if it fires off. If it doesn't work on some fields, like dates or time fields, you might need to adjust your formulas. Remember, the context is Xedit, so you can always add an additional step with the different stuff on it so the UI experience is still the preferred method. Please note that the user experience might be a bit clunky as they won't see the results until refresh, but there are pros and cons to everything.
Celigo AI
09/16/2024, 2:16 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.833262563
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.829572678
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.827902496
Celigo AI
09/16/2024, 2:16 PM