Export Scenarios

Navigates to the form selected in the Screen Name box.

An option button that indicates which access rights should be specified for the newly added form:

• Set to Granted for All Roles: The system sets the access rights for this form to Granted for all user roles in the system.
• Set to Revoked for All Roles: The system sets the access rights for this form to Revoked for all user roles in the system.
• Copy Access Rights from Screen (default): The system copies the set of the access rights from the form you specify. When you select this option button, a box appears right of it; click the magnifier icon to select the source form in the lookup table.

The dialog box has the following buttons.

The name of the scenario, which may be an alphanumeric string of up to 50 characters.

The name of the MYOB Acumatica form whose functionality will be used to perform data export.

You click the magnifier icon in the box to open the Select Screen Name dialog box where you can select the form by searching or filtering by its title, screen ID, workspace, or category.

The data provider that should be used for data export.

You can select the data provider from the list of the providers that have been created on the Data Providers (SM206015) form.

The object of the specified data provider.

Only active provider objects are available for selection.

The type of synchronization for the selected scenario.

You can select one of the following options:

• Full (default): Select this option to perform export of all the data in accordance with the scenario.
• Incremental - All Records: Select this option to perform partial export, including only the data (mentioned in the scenario) that has changed in the MYOB Acumatica records.
• Incremental - New Only: Select this option to perform partial export, including only those records that have appeared in the MYOB Acumatica database since the previous export took place.

You may need to change the default value if you use the same scenario for exporting data regularly. For example, after the initial export, you may periodically need to export new or changed data records in MYOB Acumatica to the external system or file.

A check box that indicates (if selected) that this scenario is active and can be used for data export.

A check box that indicates (if selected) that the Export by Scenario (SM207036) form for this export scenario should be available on the UI with the name specified in the Site Map Title box and in the location specified in the Workspace and Category boxes.

If you select this check box and specify the name (title) and location of the form, to open the Export by Scenario (SM207036) form for the export scenario, a user can search in the system for the site map title of the scenario or navigate to the workspace and find the processing form for the scenario under the specified category.

The name that is displayed in the UI for the Export by Scenario (SM207036) form shown for this export scenario.

This box is available only if the Make Visible on the UI check box is selected and is a required setting in this case.

The workspace in the UI from which the Export by Scenario (SM207036) form shown for the export scenario can be accessed.

This box is available only if the Make Visible on the UI check box is selected.

The name of the category under which the Export by Scenario (SM207036) form shown for the export scenario is displayed in the selected workspace.

This box is available only if the Make Visible on the UI check box is selected.

The locale whose date format (and other locale-specific formats) will be used for the data to be exported.

By default, MYOB Acumatica uses the invariant locale, which is similar to the English (United States) locale.

The mode of export of the detail lines of documents, which determines the fields that should be exported for detail records.

The value can be one of the following:

• Repeat Only Summary Fields (default): The first exported detail record contains the data of each field specified in the scenario mapping for the detail object, summary object, and related objects. The other exported detail records contained the fields of the detail object and the summary object. The fields of the related objects are blank.
• Repeat All Fields: Each exported detail record contains the data of each field specified in the scenario mapping for the detail object, summary object, and related objects.
• Do Not Repeat Fields: Only the first exported detail record contains the data of each field specified in the scenario mapping for the detail object, summary object, and related objects. The other exported records contain the data of the fields of only the detail object.

A check box that indicates (if selected) that only the fields that are mapped in the export scenario should appear in the output of data export; other fields of the data provider are skipped during export. If the check box is cleared, the fields of the data provider that are not mapped in the export scenario are exported and have null values.

We recommend that you select this check box when you are exporting data to external systems, such as HubSpot, to avoid the system rewriting of the fields that are not mapped in the scenario with null values during data export.

A check box that indicates (if selected) that the system will clear any prepared data before the data preparation and export by using the export scenario.

That is, if a user clicks the Prepare and Export button on the Export by Scenario (SM207036) form for the export scenario or the export scenario is executed based on a schedule, the system does the following, depending on whether the check box is selected:

• If the check box is selected, the system always first prepares all data for export and then exports the data.
• If the check box is cleared, and if the data for export has already been prepared during the previous data preparation and export (but this data has not been fully processed), the system performs the data export of the previously prepared data. This may prevent the scenario from being executed if there were errors during the processing of the previously prepared data.

The state of this check box for the export scenario can be overridden for any execution on the Export by Scenario (SM207036) form.

Inserts a new table row above the selected row.

Displays the form controls according to the selected option, which is one of the following: Show All Commands or Hide Service Commands.

By default, the Show All Commands option is selected, which indicates that all commands (including service commands) are displayed.

For more information on service commands, see Service Commands in Import and Export Scenarios.

Moves the selected row up the list.

Moves the selected row down the list.

Gives you the ability to insert a part of another scenario; invokes the Choose Scenario to Insert Steps From dialog box.

Opens the Substitution Lists (SM206026) form, where you can view, add, remove, and edit substitution lists, which consist of pairs of source values (which may be found in the data to be imported or exported) and the corresponding substitution values (which serve as replacements for the source values during data import to MYOB Acumatica or data export from MYOB Acumatica, respectively).

You can use the substitution lists in the SubstituteListed (sourceField, substitutionList) and SubstituteAll (sourceField, substitutionList) functions in formulas in mappings of import and export scenarios. For details about the functions, see Functions.

The scenario whose mapping lines you want to insert.

Closes the dialog box and inserts the lines from the selected scenario.

Closes the dialog box without performing insertion.

A check box that indicates (if selected) that this step of the scenario is active during data export.

The name of the functional object of the graph the MYOB Acumatica form is based on.

The functional object can be the Summary area, the Details area, or any of the tabs or dialog boxes.

The name of the field, action, or service command of the functional object selected as the Source Object.

You click the icon to select a field or action, or click the icon to open the Formula Editor Dialog Box and create a formula.

For details on the functions and operators that can be used in the formula, see Functions and Operators.

A check box that indicates (if selected) that when this field or action is filled in, a commit to the database is required.

The external field (in the target file) to hold the value to be exported.

You click the icon to select from the available external fields. You click the icon to create a formula if you want to assign its resulting value back to the internal field specified as the Field/Action Name.

A check box that indicates (if selected) that the system should ignore errors when processing the data for this field.

A check box that indicates (if selected) that the restriction is active.

The opening bracket or brackets for composing a logical expression with multiple conditions.

The field whose value the condition will be applied to.

The logical operation to apply to the value of the selected field.

The following options are available:

• Equals: Returns True if the field value is equal to the value specified in the Value field.
• Does Not Equal: Returns True if the field value is not equal to the value specified in the Value field.
• Is Greater Than: Returns True if the field value is greater than the value specified in the Value field.
• Is Greater Than or Equal to: Returns True if the field value is greater than or equal to the value specified in the Value field.
• Is Less Than: Returns True if the field value is less than the value specified in the Value field.
• Is Less Than or Equal to: Returns True if the field value is less than or equal to the value specified in the Value field.
• Is Between: Returns True if the field value is between the values specified for Value and Value 2.
• Contains: Returns True if the field value (string) contains the value specified in the Value field.
• Ends With: Returns True if the field value ends with the character or string specified in the Value field.
• Starts With: Returns True if the field value begins with the character or string specified in the Value field.
• Is Empty: Returns True if the field value is empty (null).
• Is Not Empty: Returns True if the field value is not empty (not null).
• Does Not Contain: Returns True if the field value (string) does not contain the value specified in the Value field.

If you specify a date in the Value and Value 2 box but do not specify a time, the system uses 00:00:00 or 23:59:99 as the time, depending on the condition.

If you specify date-relative parameters, such as @Today, in those boxes, the system also uses 00:00:00 or 23:59:99 as the time, depending on the condition.

The first value of the condition, which will be compared with the value of the chosen field.

Most of the conditions require only one value, while Is Between requires two values.

For data fields of the date type, you can select one of the following date-relative parameters in the Calendar dialog box:

• @Today: The business day.
• @WeekStart and @WeekEnd: The start and end of the current week. The start and end of the week are determined based on the default system locale or the locale the user has selected when signing in to MYOB Acumatica. System locales are defined on the System Locales (SM200550) form.
• @MonthStart and @MonthEnd: The start and end of the current month.
• @QuarterStart and @QuarterEnd: The start and end of the current quarter.
• @PeriodStart and @PeriodEnd: The start and end of the current financial period. The financial periods are defined on the Financial Year (GL101000) form.

  For more information about financial periods in MYOB Acumatica, see Managing Financial Periods.

• @YearStart and @YearEnd: The start and end of the current calendar year.

All the date-relative parameters use the date of the server that is used to run the MYOB Acumatica instance as the current date. Additionally, you can modify the date-relative parameters by adding or subtracting integers. The unit of measure of the parameter is determined automatically and the reference point is moved according to the measurement of the parameter—for example, @WeekStart+1 relates to the start of the next week.

The second value of the condition, if required by the selected condition.

For data fields of the date type, you can use one of the date-relative parameters, as described in Value.

The closing bracket or brackets for composing a logical expression with multiple conditions.

A logical operator to be used between the logical conditions enclosed in brackets.