How come my workflow that is set to work on view/u...
# general
d
How come my workflow that is set to work on view/update only works on update?
k
You'll have to tell more about what this workflow does for anyone to be able to have any chance of helping
d
It is meant to copy a formula field value to a field with store value = T, so the field becomes searchable. This seems to be the only way to do this per several suite answers article. According to suite answers, by setting this to execute on view and create, it should show the updated value every time the search runs, but it does not. It only executes when I edit the record, even though the trigger is set to view/update and the event for both the workflow and workflow action has 'view' selected for the event
k
You could also use a scheduled workflow to do it instead - have it run every 30 minutes/60 minutes/daily
What is the formula you are doing? There might be better ways to do what you are doing as well
d
we use zone advance billing and need to get total amount billed. It's a formula field that is calculated off of a summary search of a related record type.
shows up fine obviously in the UI, but blank in searches. I could probably have the search include the same summary lookup, but I wanted to provide an easy way for everyone to get the data as we don't have many power users.
It really sucks that fields with default formula values don't render in search
k
Yeah, a scheduled workflow is probably your best bet.
Or a user event script that runs on your billing transaction to update the original record.
Since the billing isn't actually on the record itself you can't use workflow
d
second is probably preferrable as always ensures accuracy
k
Side note - is this on a Sales Order?
d
nah, they have their own custom record type called zab subscription which has a related custom record called zab charges
those later get reconcilled into sales orders during a 'create transaction' stage
k
Right.
d
but initially, the subscription is the source record
k
Just wanted to make sure you weren't building something to accommodate for what should already natively exist in NS.
So it'd be a user event script on your invoices to update the ZAB Subscription record.
and it'd probably have to be triggered in a Map/Reduce script
which shouldn't be too hard
Since you can get a summary saved search - the two records have to be linked somehow.