Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Save record changes before at script start

Featured Replies

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

  • Author

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

  • Author

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

Commit Records/Requests

Commit Records/Requests

Commit Records/Requests

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.