[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

FM - Auto Entry Modification Data Entering When Scheduled Script Runs

Posted on 2012-08-29
4
Medium Priority
?
626 Views
Last Modified: 2012-09-05
If using a non-global field (which thus exists on every record), is there a way of running a scheduled script which modifies this field, but does not change the auto-entry Modification data and name fields?
0
Comment
Question by:rvfowler2
  • 2
4 Comments
 
LVL 9

Expert Comment

by:jvaldes
ID: 38350126
Use the replace function from inside a script. That will allow you to impact all found records with any calculation you may like at the time you run the script. Make sure you set the autoenter field to allow modification.
0
 
LVL 25

Assisted Solution

by:Will Loving
Will Loving earned 1000 total points
ID: 38350201
I think what Randy is looking for is to prevent the separate Auto-enter Modification Date and User fields from firing when he modifies a field in the same record. I think if you're using the Modification Date and Modification User options built into FM, then any change you make to the record is going to affect these fields. You might be able to do something by changing the Modification fields to Auto-enter by calculation and including a Case( ) to always update except when a Variable flag $DontUpdate is set in the script. However, this would require a calculation that functioned similarly to the built-in Modification Auto-enter feature and while I'm sure there is probably a way to do that, I can't think of what it would be right now.

You might be able to keep your existing Modification fields and make a second set that is displayed to end users. Set an Auto-Enter calculation to Auto-enter whatever is in the Modification Date or User field unless the $DontUpdate flag is set. Haven't tested this but it would be simple enough to try.
0
 
LVL 2

Accepted Solution

by:
rvfowler2 earned 0 total points
ID: 38354706
Will has it right.  Thanks for these suggestions.  The solution I came up with is to never use a non-global field (one for every record) as a flag for a scheduled script.  Instead, I assigned a script parameter and used that, but you could also use a global variable, etc.  While you would not be able to do that in every case, I was able to get rid of the field here.
0
 
LVL 2

Author Closing Comment

by:rvfowler2
ID: 38367116
Giving Will credit for solutions that I could use at another time.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Pop up windows can be a useful feature of any Filemaker database.  Though best used sparingly, they can be employed in a multitude of different ways, for example;  as a splash screen at login, during scripted processes to control user input, as pick…
Conversion Steps for merging and consolidating separate Filemaker files The following is a step-by-step guide for the process of consolidating two or more FileMaker files (version 7 and later) into a single file with multiple tables. Sometimes th…
Screencast - Getting to Know the Pipeline
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question