Parameters
DayBackForFileMaker.Parameters History
Hide minor edits - Show changes to output
Added lines 4-5:
You can tell a script accepts parameters using the "hash" function if they begin with a Set Variable step that uses the "#Assign" or "#AssignGlobal" custom function.
April 15, 2020, at 03:36 PM
by - Formatting
Changed lines 1-22 from:
!! Passing Parameters to DayBack's built-in scripts !!
-> Many of the scripts in DayBack accept multiple parameters for use within thescript. To pass these parameters in a standard way, DayBack uses the "hash" (#) custom functions.
''' Using the hash function '''
-> To use this function in your parametercalculation, you can first type the # character and press tab to see the template auto-populate, looking like this:
--># ( name ; value )
-> Replace the '''''name''''' placeholder with the name of the parameter you're providing as a string, like "sc_Mode".
-> Replace the '''''value''''' placeholder with the actual value of the parameter.
-> Here's an example of passing a parameter to navigate the calendar to Month view starting 30-days ago. More examples can be found in the [[Navigation | navigation docs here]]
--> #("sc_Mode" ; "Month") & #("sc_FocusDate" ; Get ( CurrentDate ) - 30 )
''' Copying the functions into your file '''
->These are already included with the DayBack file, and copying them to your file when embedding is already part of the integration process. But, if you need to perform some of the scripts in DayBack's file from a script in your file, you may need to copy over the custom functions.
-> Many of the scripts in DayBack accept multiple parameters for use within the
-> To use this function in your parameter
-
-
->
to:
!! Passing Parameters to DayBack's built-in scripts
Many of the scripts in DayBack accept multiple parameters for use within the script. To pass these parameters in a standard way, DayBack uses the "hash" (#) custom functions.
!! Using the hash function
To use this function in your parameter calculation, you can first type the # character and press tab to see the template auto-populate, looking like this:
-># ( name ; value )
\\
Replace the '''''name''''' placeholder with the name of the parameter you're providing as a string, like "sc_Mode".
Replace the '''''value''''' placeholder with the actual value of the parameter.
Here's an example of passing a parameter to navigate the calendar to Month view starting 30-days ago. More examples can be found in the [[Navigation | navigation docs here]]
-> #("sc_Mode" ; "Month") & #("sc_FocusDate" ; Get ( CurrentDate ) - 30 )
!! Copying the functions into your file
These are already included with the DayBack file, and copying them to your file when embedding is already part of the integration process. But, if you need to perform some of the scripts in DayBack's file from a script in your file, you may need to copy over the custom functions.
Many of the scripts in DayBack accept multiple parameters for use within the script. To pass these parameters in a standard way, DayBack uses the "hash" (#) custom functions.
!! Using the hash function
To use this function in your parameter calculation, you can first type the # character and press tab to see the template auto-populate, looking like this:
-># ( name ; value )
\\
Replace the '''''name''''' placeholder with the name of the parameter you're providing as a string, like "sc_Mode".
Replace the '''''value''''' placeholder with the actual value of the parameter.
Here's an example of passing a parameter to navigate the calendar to Month view starting 30-days ago. More examples can be found in the [[Navigation | navigation docs here]]
-> #("sc_Mode" ; "Month") & #("sc_FocusDate" ; Get ( CurrentDate ) - 30 )
!! Copying the functions into your file
These are already included with the DayBack file, and copying them to your file when embedding is already part of the integration process. But, if you need to perform some of the scripts in DayBack's file from a script in your file, you may need to copy over the custom functions.
Changed line 26 from:
to:
Open Dayback.fmp12 and navigate to "File -> Manage -> Custom Functions". Select all of the custom functions ('''there are three''') by shift-clicking and copy them (edit -> copy). Then go back to your file and open up the custom function dialog "File -> Manage -> Custom Functions" and paste all of the custom functions you have just copied.
April 15, 2020, at 03:33 PM
by - Added Parameters doc
Added lines 1-25:
!! Passing Parameters to DayBack's built-in scripts !!
-> Many of the scripts in DayBack accept multiple parameters for use within the script. To pass these parameters in a standard way, DayBack uses the "hash" (#) custom functions.
''' Using the hash function '''
-> To use this function in your parameter calculation, you can first type the # character and press tab to see the template auto-populate, looking like this:
--># ( name ; value )
-> Replace the '''''name''''' placeholder with the name of the parameter you're providing as a string, like "sc_Mode".
-> Replace the '''''value''''' placeholder with the actual value of the parameter.
-> Here's an example of passing a parameter to navigate the calendar to Month view starting 30-days ago. More examples can be found in the [[Navigation | navigation docs here]]
--> #("sc_Mode" ; "Month") & #("sc_FocusDate" ; Get ( CurrentDate ) - 30 )
''' Copying the functions into your file '''
-> These are already included with the DayBack file, and copying them to your file when embedding is already part of the integration process. But, if you need to perform some of the scripts in DayBack's file from a script in your file, you may need to copy over the custom functions.
-> ''This step requires FileMaker Advanced. If you don't have FileMaker Advanced, please [[https://www.seedcode.com/contact/ | get in touch]] and we'd be happy to get a copy of your files and perform this step for you.''
-> Open Dayback.fmp12 and navigate to "File -> Manage -> Custom Functions". Select all of the custom functions ('''there are three''') by shift-clicking and copy them (edit -> copy). Then go back to your file and open up the custom function dialog "File -> Manage -> Custom Functions" and paste all of the custom functions you have just copied.
-> Many of the scripts in DayBack accept multiple parameters for use within the script. To pass these parameters in a standard way, DayBack uses the "hash" (#) custom functions.
''' Using the hash function '''
-> To use this function in your parameter calculation, you can first type the # character and press tab to see the template auto-populate, looking like this:
--># ( name ; value )
-> Replace the '''''name''''' placeholder with the name of the parameter you're providing as a string, like "sc_Mode".
-> Replace the '''''value''''' placeholder with the actual value of the parameter.
-> Here's an example of passing a parameter to navigate the calendar to Month view starting 30-days ago. More examples can be found in the [[Navigation | navigation docs here]]
--> #("sc_Mode" ; "Month") & #("sc_FocusDate" ; Get ( CurrentDate ) - 30 )
''' Copying the functions into your file '''
-> These are already included with the DayBack file, and copying them to your file when embedding is already part of the integration process. But, if you need to perform some of the scripts in DayBack's file from a script in your file, you may need to copy over the custom functions.
-> ''This step requires FileMaker Advanced. If you don't have FileMaker Advanced, please [[https://www.seedcode.com/contact/ | get in touch]] and we'd be happy to get a copy of your files and perform this step for you.''
-> Open Dayback.fmp12 and navigate to "File -> Manage -> Custom Functions". Select all of the custom functions ('''there are three''') by shift-clicking and copy them (edit -> copy). Then go back to your file and open up the custom function dialog "File -> Manage -> Custom Functions" and paste all of the custom functions you have just copied.