https://netsuiteprofessionals.com logo
Join SlackCommunities
Powered by
We need to change calendars (using multi-calendar)...
# suiteflow
r
We need to change calendars (using multi-calendar) periodically due to an acquisition. We obviously don't want to give a bunch of people edit access to the Subsidiary record, which is where the calendar setting lives. I thought this would be a simple workflow. Set it up so when someone brings up the Subsidiary record, there are two buttons-"Switch to Calendar A" and "Switch to Calendar B." Pressing the respective button would set the Fiscal Calendar and Tax Fiscal Calendar to those values. I set simple transitions to go to the proper WF step based on which button gets pushed and that step should set the field to the respective calendar values. But it doesn't. In looking at the logging, while it seems to recognize the button push, it's not transitioning. I didn't have a "Transition On" value on the transition records, because I don't recall ever having to have that when you have an Execute on Button value; there's nothing set there on a JE workflow we have that uses buttons. Without the Transition On value, I can see a "Considered" option in the logging where it's not transitioning because the Transition On value is missing. So I tried setting all the possible Transition On values and on each, it no longer is showing that Considered line, but it's not transitioning either. I have this set to Execute as Admin. Any ideas?
m
Is there a condition on your transition?
r
Nope
I mean I guess technically there was in that I had specified only the UI context. I just selected all Contexts though and still same behavior. Transition record could not be more simple. I just have the Execute on Button filled in and Transition On due to my note above. Otherwise nothing.
m
Can you send me a screenshot of the transition setup in your workflow? (if you don't mind)?
r
Sure
I don't recall ever having to set a Transition On value using a button previously, but if I don't, this is what I get in the logging.
Maybe the subsidiary record has some unique properties under the hood that causes there to be special requirements? I dunno. I don't recall ever trying to run a WF on a Sub record before, but I'd think it shouldn't be significantly different than a Customer or Vendor.
m
What is that check action allowed for execution context: null line in the logs ?
I don’t remember seeing that ever
r
I don't either, but "execution context" apparently refers to that Transition On field because that message goes away when I set a Transition On value. Why the WF is checking (or cares) why that field is filled in before it will go forward, I have no idea.
m
Yeah that is so weird. I’ve never seen that
Does your add button action have any context limitations?
r
Great I'm finding new bugs. Lucky me....ha
Does your add button action have any context limitations?
It was filtered to the UI yeah. I just tried it with all contexts selected and no dice. I've tried it also with Save Record First (which shouldn't apply here) and Check Condition Before Execution (which also shouldn't) both on and off. No change.
m
Maybe try this
Add a new button called “test” but don’t mess with any other settings other than the name
Then add a new transition but don’t change any setting other than the execute on button = test
See if that produces the same error or problem
r
wtf that works. I mean I'm glad, but why tf didn't the others work
I confused it by (checks notes) changing values?!
m
Haha yeah I think something happened in the initial config of the button or transition that corrupted it. /confused it
Maybe NetSuite still has a case of the Mondays from the long weekend
r
I wonder if it was our 2024.2 prep mini update. We had that over the weekend and we've seen a few funky things going on.
Appreciate your time and help!
m
Could be, sometimes NetSuite is a mystery. lol Happy to help anytime. Have a great week
5 Views
Open in Slack
PreviousNext
Powered by