Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7203 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hello, I've run into a problem with the population of data in the lookup fields in a related record which is generate by a scripted button. My research shows me that when the data entry to the main record "Jobs" does not have the enter key pushed prior to hitting the scripted button which creates a related record "Work Order", then some of the lookup fields in the Work Order do not population.

Is there a script step I can put at the beginning of my script attached to the button that will make sure the data in the original record has been saved? Or is there another way. I've already tried to have the record changes be required to have a manual save rather than automatic under the layout setup, but that didn't correct the problem.

Please help! ooo.gif

Posted

Hello, I've run into a problem with the population of data in the lookup fields in a related record which is generate by a scripted button. My research shows me that when the data entry to the main record "Jobs" does not have the enter key pushed prior to hitting the scripted button which creates a related record "Work Order", then some of the lookup fields in the Work Order do not population.

Is there a script step I can put at the beginning of my script attached to the button that will make sure the data in the original record has been saved? Or is there another way. I've already tried to have the record changes be required to have a manual save rather than automatic under the layout setup, but that didn't correct the problem.

Please help! ooo.gif

Posted

Hello, I've run into a problem with the population of data in the lookup fields in a related record which is generate by a scripted button. My research shows me that when the data entry to the main record "Jobs" does not have the enter key pushed prior to hitting the scripted button which creates a related record "Work Order", then some of the lookup fields in the Work Order do not population.

Is there a script step I can put at the beginning of my script attached to the button that will make sure the data in the original record has been saved? Or is there another way. I've already tried to have the record changes be required to have a manual save rather than automatic under the layout setup, but that didn't correct the problem.

Please help! ooo.gif

This topic is 7203 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.