Adds the two operands and returns the result. If at least one operand is a string, this operator returns a concatenated string.

Example: =[Amount]+[VAT amount]

In this example, the [Amount] and [VAT amount] values are used as operands.

Subtracts the second operand from the first.

Example: =[Amount]-[Cash discount]

In this example, the [Amount] and [Cash discount] values act as operands.

Multiplies the two operands.

Example: =[Chargeable amount]*0.03

In this example, the [Chargeable Amount] value and the number 0.03 serve as operands.

Yields the quotient of the operands, which is the first operand divided by the second.

Example: =[Amount]/[Rate reciprocal]

In this example, the [Amount] and [Rate reciprocal] values are the first and second operands.

Divides the first integer operand by the second integer operand and returns the remainder, rounded to the nearest integer.

Example: =[Volume] Mod [Conversion factor]

In this example, the [Volume] and [Conversion factor] values are used as operands.

Performs logical conjunction on two Boolean expressions: returns True if and only if both expressions evaluate to True; in other cases, returns False.

Example: =[Hold] And [Validate control totals on entry]

In this example, the [Hold] and [Validate control totals on entry] check boxes are used as operands.

Performs logical disjunction on two Boolean expressions: returns True if at least one expression evaluates to True; returns False if neither expression evaluates to True.

Example: =[Hold] Or [Validate control totals on entry] In this example, the [Hold] and [Validate control totals on entry] check boxes act as operands.

Performs logical negation on a Boolean expression: returns True if and only if the operand is False. Logical negation is an unary operator.

Example: =Not [Hold documents on entry]

In this example, the [Hold documents on entry] check box is used as the single operand.

Returns True if operands are equal.

Example: =([Credit total] = [Control total])

In this example, the [Credit total] and [Control total] values are used as operands.

Returns True if operands are not equal.

Example: =([Credit total] <> [Debit total])

In this example, the [Credit total] and [Debit total] values act as operands.

Returns True if the first operand is less than the second one.

Example: =([DocDate] < [DueDate])

In this example, the [DocDate] and [DueDate] values act as operands.

Returns True if the first operand is greater than the second one.

Example: =([CrLmt] > 1000])

In this example, the [CrLmt] value is used as the first operand, and the number 1000 acts as the second operand.

Returns True if the first operand is less than or equal to the second operand.

Example: =(([DueDate]-[CashDiscountDate]) <= [LeadTime])

In this example, [DueDate] - [CashDiscountDate] is the first operand, and the [LeadTime] value is used as the second operand.

Returns True if the first operand is greater than or equal to the second operand.

Example: =([Balance] => [Amount])

In this example, the [Balance] and [Amount] values are used as operands.

An operator that returns True if the second operand (a string) contains the first operand (which is also a string).

Example: =('Inc.' In [Supplier name])

In this example, the [Supplier name] value is used as an operand, and the formula returns True if the name of the supplier contains Inc.

A binary constant used as an operand in logical expressions.

Example: =True

A binary constant used as an operand in logical expressions.

Example: =False

A special value used as an operand in logical expressions; designates an undefined value.

Example: =Null

Converts the expression used as the function argument into a Boolean expression. Returns False if the Boolean value is zero; otherwise, returns True.

Example: =CBool([CashDiscountAmount]

Here [CashDiscountAmount] is used as the function argument.

Converts the expression used as the function argument into a value of the Date type. The argument should be a valid date expression according to the locale selected for the import or export scenario.

Example: =CDate('24/12/2011')

Here a string is used as the function argument.

Converts the expression used as the function argument into a string. If the argument is Null, the function returns a run-time error; otherwise, it returns a string.

Example: ='(' +CStr([AreaCode])+')'+CStr([Phone])

Here [AreaCode] and [Phone] are used in the function argument.

Converts the expression defined in the function argument into a value of the Double type.

Example: =CDbl(1.0/[ExchangeRate])

Here [ExchangeRate] is used in the function argument.

Converts the expression used as the function argument into a value of the Single type. If the expression has a value outside the acceptable range for the Single type, this function returns an error.

Example: =CSng([CashDiscountAmount]/[DocAmount])

Here [CashDiscountAmount] and [DocAmount] are used in the function argument.

Converts the expression used as the function argument into a value of the Decimal type.

Example: =CDec([DocAmount]*0.015)

Here [DocAmount] is used in the function argument.

Converts the expression used as the function argument into a value of the Integer type.

Example: =CInt('2012')-Year([DocDate])

Here [DocDate] is used in the function argument.

Converts a numeric value to a value of the Short type.

Example: =CShort([CashDiscountAmount])

Here [CashDiscountAmount] is used as the function argument.

Converts a numeric value to a value of the Long type.

Example: =CLong([CashDiscountAmount])

Here [CashDiscountAmount] is used as the function argument.

Removes all leading spaces or parsing characters from the specified string, or all leading zero bytes (0) from the specified binary expression.

Example: =LTrim(CStr([Phone]))

Here [Phone] is used as the function argument.

Removes all trailing spaces or parsing characters from the specified character expression, or all trailing zero (0) bytes from the specified binary expression.

Example: =RTrim(CStr([AreaCode]))

Here [AreaCode] is used as the function argument.

Removes all leading and trailing spaces or parsing characters from the specified character expression, or all trailing zero (0) bytes from the specified binary expression.

Example: =Iif(Trim([Country])

Here [Country] is used in the function argument.

Replaces the format item in a specified formatting string ( format ) with the text equivalent of the arguments ( arguments ).

Example: =Format('Currency:........ {0:C}; Account:........ {1:N}', [Currency], [AccountBalance])

Here [Currency] and [AccountBalance] are used in the function argument; 0 and 1 are the specifiers indicating where the arguments will be inserted, C is the currency format specifier, and N is the number format specifier.

Returns a string that has been converted to uppercase. The string argument can be any valid string expression. If string contains Null, Null is returned.

Example: =UCase([CustomerName])

Here [CustomerName] is used as the function argument.

Returns a string that has been converted to lowercase. The string argument can be any valid string expression. If string contains Null, Null is returned.

Example: =LCase(CStr([CustomerID])

Here [CustomerID] is used in the function argument.

Returns the position of the first occurrence of one string ( findString ) within another ( string ).

Example: =InStr([CustomerName], 'Inc')

Here [CustomerName] is used in the function argument.

Returns the position of the last occurrence of one string ( findString ) within another ( string ).

Example: =InStrRev([CustomerName], 'Inc')

Here [CustomerName] is used in the function argument.

Returns an integer containing either the number of characters in the string or the nominal number of bytes required to store a variable.

Example: =Len([CustomerName])

Here [CustomerName] is used as the function argument.

Returns a string containing the specified number of characters from the left side of a string. If string contains Null, Null is returned.

Example: =Left(Trim([VendorName]), 10)

Here [VendorName] is used in the function argument.

Returns a string containing a specified number of characters from the right side of a string. If string contains Null, Null is returned.

Example: =Right(CustomerName, 3)

Here [CustomerName] is used in the function argument.

Returns a string in which the specified substring ( oldValue ) has been replaced with another substring ( newValue ).

Example: =Replace([Description], 'rur', 'eur')

Here [Description] is used in the function argument.

Right-aligns the characters in a specified string (string), padding with the specified character (paddingChar) on the left up to the specified total width (width). If the actual length of the string is less than the specified width, returns the original string.

Example: =PadLeft(CStr(Phone), 12, '_')

Here [Phone] is used in the function argument. If the actual length of the string is less than the specified width, returns the original string.

Left-aligns the characters in a specified string ( string ), padding with the specified character ( paddingChar ) on the right up to the specified total width ( width ).

Example: =PadRight(CStr([City]), 25, '_')

Here [City] is used in the function argument. If the actual length of the string is less than the specified width, returns the original string.

Returns the absolute value of the number.

Example: =Abs([TotalDebit]-[TotalCredit])

Here [TotalDebit] and [TotalCredit] are used in the function argument.

Returns the largest integer that is not greater than the argument.

Example: =Floor([Price]/([Cost])

Here [Price] and [Cost] are used in the function argument.

Returns the smallest integer that is not less than the argument.

Example: =Ceiling([Price]/[Cost])

Here [Cost] and [Price] are used in the function argument.

Returns a numeric expression, rounded to the specified precision ( decimals ).

Example: =Round(([Price]-[Cost])/[Cost], 2)

Here [Cost] and [Price] are used in a function argument, and 2 is the number of decimal places.

Returns the smaller of the two values.

Example: =Min([Price],[Cost])

Here [Cost] and [Price] are used in the function argument.

Returns the greater of the two values.

Example: =Max({StandardCost],[AvrCost])

Here [StandardCost] and [AvrCost] are used in the function argument.

Computes the value of x raised to the specified power ( power ).

Example: =Pow(([Markup], 2))

Here [Markup] is used in the function argument; the function returns the mark-up value squared (or to the second power).

Returns the current date and time according to the system date and time on the local computer.

Example: =Now()

Returns the current date according to the system date and time on the local computer.

Example: =Today()

Returns the current date and time according to the user’s time zone.

The system gets the user’s time zone from the following sources, which are ordered by the priority from the highest to the lowest:

1. User’s preferences specified in the User profile (SP203010) window.
2. The employee calendar specified in the Work calendar (CS209000) window and selected for the user’s employee in the Employees (EP203000) window.

Example: =NowUTC()

Returns the current date according to the user’s time zone.

The system gets the user’s time zone from the following sources, which are ordered by the priority from the highest to the lowest:

1. User’s preferences specified in the User profile (SP203010) window.

2. The employee calendar specified

1. The employee calendar specified in the Work calendar (CS209000) window and selected for the user's employee in the Employees (EP203000) window.

Example: =TodayUTC()

Returns a new date calculated by adding the specified number ( nbr ) of time intervals ( int ) to the date ( dt ). The int argument specifies the type of time interval and is one of the following options:

yyyy

A number ( nbr ) of years will be added to the specified date ( dt ).

m

A number ( nbr ) of months will be added to the specified date ( dt ).

y

Same as d; see below.

d

A number ( nbr ) of days will be added to the specified date ( dt ).

h

A number ( nbr ) of hours will be added to the specified date ( dt ).

n

A number ( nbr ) of minutes will be added to the specified date ( dt ).

s

A number ( nbr ) of seconds will be added to the specified date ( dt ).

Examples:

• =DateAdd([StartPeriod], 'm', 12)
• =DateAdd([CashDiscountDate], 'd', -2)

In these examples, [CashDiscountDate] and [StartPeriods] are used in the function arguments.

Returns the year, as an integer, extracted from the specified date ( date ).

Example: =Year([StartPeriod])

Here [StartPeriod] is used as the function argument.

Returns the month, as an integer, extracted from the specified date ( date ).

Example: =Month([StartPeriod])

Here [StartPeriod] is used as the function argument.

Returns the day (as an integer) extracted from the specified date ( date ).

Example: =Iif(Day([DueDate]-[LeadTime])=0, True, False

Here [DueDate] and [LeadTime] are used in the function argument.

Returns the day of the week associated with the specified date ( date ) as an integer.

Example: =DayOfWeek([StartPeriod])

Here [StartPeriod] is used as the function argument.

Returns the day of the year calculated for the specified date ( date ).

Example: =DayOfYear([StartPeriod])

Here [StartPeriod] is used as the function argument.

Returns the number of minutes extracted from the specified date ( date ).

Example: =Minute([StartPeriod])

Here [StartPeriod] is used as the function argument.

Returns the seconds extracted from the specified date ( date ) as an integer.

Example: =Second([StartPeriod])

Here [StartPeriod] is used as the function argument.

Returns one of two values, depending on the evaluation of the expression: If the expression evaluates to True, the function returns the truePart value; otherwise, it returns the falsePart value.

Example: =IIf(([CurrencyID]='', 'USD', [CurrencyID])

Here [CurrencyID] is used in the function argument.

Returns the value value_n that corresponds to the first expression expression_n that evaluates to True. expression_1, expression_2, and so on are Boolean expressions.

Example: =Switch(([DocAmount]<100), 'small', (([DocAmount]>=100)And([DocAmount]<500)), 'medium',(([DocAmount]>=500)And([DocAmount]<1000)),'large')

Here [DocAmount] is used in the function argument.

Replaces NULL with the specified replacement value. The value argument is to be checked for NULL.

Example: =IsNull([CustomerID],'NULL value') Here, [CustomerID] is used in the function argument.

Calculates the hash string for the specified string.

Example: =Provider.CalculateHash([CUSTOMER ID] + [INVOICE REF NBR] + [LINE NBR])

In this example, the hash string is calculated for the string that contains concatenated values of the [CUSTOMER ID], [INVOICE REF NBR], and [LINE NBR] fields.

Calculates the hash code (which is an Integer value) for the specified string.

Example: =Provider.CalculateHash([CUSTOMER ID] + [INVOICE REF NBR] + [LINE NBR])

In this example, the hash code is calculated for the string that contains concatenated values of the [CUSTOMER ID], [INVOICE REF NBR], and [LINE NBR] fields.

The type of provider, such as the following:

• File providers that you use to access data in external files:

  • CSV provider ( PX.DataSync.CSVSYProvider ): For import from and export to files in CSV format
  • Excel provider ( PX.DataSync.ExcelSYProvider ): For import from and export to Excel spreadsheets
  • XML provider ( PX.DataSync.XMLSYProvider ): For import from and export to files in XML format

• Providers that are preconfigured for importing data from and exporting data to external systems:

  • Salesforce provider ( PX.DataSync.SFSYProvider ): For import from and export to SalesForce CRM by using the Simple Object Access Protocol (SOAP)
  • MS SQL provider ( PX.DataSync.MSSqlSYProvider ): For import from and export to Microsoft SQL Server
  • HubSpot provider ( PX.DataSync.HubSpot.HSSYProvider ): For exporting leads to HubSpot for nurturing and importing leads to Visma Net for processing

• Providers for exporting payment data to external payment systems:

  • ACH provider ( PX.DataSync.ACHProvider ): For exporting data for processing in the Automated Clearing House (ACH) system
  • Giro payment provider ( PX.DataSync.Banks.GIROPaymentProvider ): For exporting data for processing in giro-based payment systems

The name of the parameter, which is specific to the provider type.

A CSV provider uses the following parameters:

• The FileName parameter, which is standard for file providers, specifies the name of the file that should be used for data import or data export. The path to the file is set automatically after you have uploaded an external file to the provider.
• The Encoding parameter specifies the encoding of the source file. You can select the proper encoding value from the drop-down list in the Value column of the table on the Parameters tab. By default, the value of the parameter is set to US-ASCII.
• The Delimiter parameter specifies the delimiter that is used in the CSV file. You can use as a delimiter any printable character. By default, a comma (,) is used as the delimiter.
• The QuoteAll parameter makes the provider enclose all values from the source file in double quotes. By default, the system does not enclose source values in double quotes.

An Excel provider uses the following parameters:

• The FileName parameter, which is standard for file providers, specifies the name of the file that should be used for data import or data export.

An XML provider uses the following parameters:

• The FileName parameter, which is standard for file providers, specifies the name of the file that should be used for data import or data export.

• The Encoding parameter specifies the encoding of the source file. You can select the proper encoding value from the drop-down list in the Value column of the table on the Parameters tab. By default, the value of the parameter is set to US-ASCII.

• The Format parameter specifies the format of the XML file. There are two options:

  • Tree: The source file has a tree structure; that is, the values of the source fields are placed in tags of the source XML file. This is the default option.
  • Flat: The source file has a flat structure; that is, the values of the source fields are placed in attributes of tags in the source XML file.

A Microsoft SQL provider uses the following parameters:

• Server: Specifies the location of the Microsoft SQL Server instance. This is a required parameter. You set the parameter to the server name for a default instance of Microsoft SQL Server (for example MyServer ), and to the server name and instance name for a named instance of Microsoft SQL Server (for example, Myserver\MyInstance). If a default instance of Microsoft SQL Server is installed on the same computer where Visma Net is installed, you can set the value of the parameter to (local).

• Database: Specifies the name of the database on the server. This is a required parameter.

• Login: Specifies the login for accessing the Microsoft SQL Server database. This is a required parameter.

• Password: Specifies the password for accessing the Microsoft SQL Server database. This is a required parameter.

• LastModifiedDateColumn: Specifies the column of the database table or view that contains the date when the record was most recently modified. This parameter is necessary only if you want Visma Net to use the synchronisation type of an import scenario based on the Microsoft SQL provider. For details on the synchronisation types, see the description of the Sync type field in the Manage import scenarios (SM206025) topic.

• CreatedDateColumn: Specifies the column of the database table or view that contains the date when the record was created. This parameter is necessary only if you want Visma Net to use the synchronisation type of an import scenario based on the Microsoft SQL provider. For details on the synchronization types, see the description of the Sync type field in the Manage import scenarios (SM206025) topic.

• Authentication: Defines the authentication type to be used to connect to the database server. There are two options:

  • SQL: Visma Net connects through SQL Server authentication. The account you specify should have sufficient rights for making changes to the database. This authentication type is used by default.
  • Windows: Visma Net connects through a Windows user account with the login and password you provide. Windows authentication works only for a local Microsoft SQL Server or when both application and database servers are members of the same Windows domain.

Opens the Object command editor dialog bo x, where you can type the commands for the selected table line.

Click Close to save the command and close the dialog box.

This button is used for only SQL data providers.

The command to be executed for the object during data preparation.

For example: You can apply SQL commands to source objects to apply restrictions on the imported records, select particular records from the source database table, or join data from several tables into one object in the data provider.

This column is used for only SQL data providers.

Opens the Object command editor dialog box, where you can type the commands for the selected table line.

Click Close to save the command and close the dialog box.

This button is used for only SQL data providers.

A check box that indicates (if selected) that the field contains the key to the data set of the object.

Currently this column is not used by data providers.

The type of data in the field, which can be one of the following options: String, DateTime, Double, Decimal, Boolean, or Int32.

For SQL data providers, the value of this field is filled in automatically from the corresponding property of the columns of SQL tables. For other provider types, you do not need to set the value in this column.

The length of the data in the field.

For SQL data providers, the value of this field is filled in automatically from the corresponding property of the columns of SQL tables. For other provider types, you do not need to set the value in this column.

The action to be performed on the field data during data preparation. For example: You can replace the value of a field with some calculated value, or change the value of a field depending on some condition.

This column is only used for SQL data providers.

A read-only field showing the status of the selected scenario, which is automatically assigned during the processing and can be one of the following options:

New

Indicates that this scenario is either new and has not been used for data preparation or that the history of processing for this scenario has been rolled back.

Prepared

Indicates that the data has been prepared in accordance with the scenario.

Partially processed

Means that the data for the scenario has been processed only partially.

Processed

Indicates that the data for the scenario has been processed completely.

A read-only field that shows the type of synchronization for the selected scenario, which can be one of the following options:

Full

Performs export of all the data in accordance with the scenario.

Incremental: all records

Performs partial export, including only the data (mentioned in the scenario) that has changed in the Visma Net records.

Incremental: new only

Performs partial export, including only those records that have appeared in the Visma Net database since the previous export took place.

A check box that you select to not export the titles of the elements in the window.

You specify this option for a particular execution of a scenario. That is, the selected value is discarded after each execution of the scenario or each refresh of the page.

In the drop-down list you have the following options:

• Add Once a schedule is added to this window, the following options are also available:

This opens the Automation schedules (SM205020) window as a pop-up. Here you can create and add automation schedules. For more information, see: Schedule processing.

• History
• Delete
• Delete all
• View

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.

The type of synchronisation for the selected scenario, which can be one of the following options:

Full

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 Visma Net records.

Incremental - new only

Select this option to perform partial export, including only those records that have appeared in the Visma Net database since the previous export took place.

Displays the window 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.

The external field (in the target file) to hold the value to be exported. Click the icon to select from the available external fields.

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.

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 null

Returns True if the field value is null.

Is not null

Returns True if the field value is not null.

Does not contain

Returns True if the field value (string) does not contain the value specified in the Value field.

The operation to be performed for the scenario or scenarios selected in the Scenarios area. Select one of the following options:

Prepare and export

Prepares and exports the data in one step.

Prepare

Only prepares the data for export (without exporting it); select this option if the data may require manual editing.

Export

Exports the already-prepared data.

Roll back

Rolls back the data prepared for export or removes the prepared data from the Prepared data dialog box and the latest record from the history of scenario processing in the Mapping history dialog box.

The operation to be performed for the scenarios selected in the table. The following options are available:

Prepare and import

Select this operation to prepare and import the data in one step.

Prepare

Select this operation to only prepare (but not import) the data for import if the data may require manual editing.

Import

Select this operation to only import (but not prepare) the already-prepared data.

Roll-back

Select this operation to roll back the data prepared for import or remove the prepared data from the Prepared data dialog box and remove the latest record from the history of scenario processing in the History dialog box.

A check box that indicates (if selected) that only data validation will be performed.

The scenario processing emulates data import and is cancelled if an error occurs.

If you want to save the imported data after successful validation, select the Save if data is valid check box.

A check box that indicates (if selected) that the data should be saved if it is valid.

Clear the check box if you don’t want to save the data after import validation.

This option is available only when you select the Validate data (no saving) check box to switch to import validation mode.

The status of the scenario, as automatically assigned during the processing. The status can be one of the following options:

Prepared

Indicates that the data has been prepared in accordance with the scenario

Partially processed

Indicates that the data for the scenario has been imported only partially

Imported

Indicates that the data for the scenario has been imported completely

Gives you the ability to add a new simplified import scenario.

Clicking this button first opens the Select file for import dialog box, where you can select the file whose data you want to import, and then opens the Provide new scenario properties dialog box, where you select the window to be used for data import, name the scenario, and select the data provider type.

Required. The Visma Net form to be used for importing data from the uploaded file.

You select the window name by finding its workspace, finding its section, and selecting the applicable form in the site tree.

Required. The name of the new simplified import scenario.

The system generates the name automatically, based on the title of the form you selected in the Window name field. If required, you can change the name.

A read-only element that shows the status of the selected scenario, which is automatically assigned during the processing and can be one of the following options:

New

Indicates either that this scenario is new and has not been used for data preparation or that the history of processing for this scenario has been rolled back.

Prepared

Indicates that the data has been prepared in accordance with the scenario.

Partially processed

Indicates that the data for the scenario has been imported only partially.

Processed

Indicates that the data for the scenario has been imported completely.

A check box that you select to prepare and import data regardless of the status and the results of the previous import.

Generally, you should select this check box if you are scheduling the processing of the selected scenario and you expect errors during the import that do not affect the performance of the scenario.

For example: The system returns an error for a line when it is trying to import a line that has been imported in the previous cycle. If you select the check box, the system can run the scenario on a schedule, thus importing the new lines. If you clear the check box, the system won’t be able to run the scenario on schedule if the previous processing of the scenario returned errors.

For more information about scheduling, see: About scheduled processing.

A read-only box that displays the data provider of the selected import scenario.

To view the details of the provider, click the button to the right of the field to open the Data providers (SM206015) window.

A read-only box that shows the type of synchronisation for the selected scenario, which can be one of the following options:

Full

Performs export of all the data in accordance with the scenario.

Incremental: all records

Performs partial export, including only the data (mentioned in the scenario) that has changed in the Visma Net records.

Incremental: new only

Performs partial export, including only those records that have appeared in the Visma Net database since the previous export took place.

A check box that indicates (if selected) that the processing will be cancelled if an error occurs.

You specify this option for a particular execution of a scenario. That is, the selected value is discarded after each execution of the scenario or each refresh of the page.

This check box affects the order in which the records are imported. For example: Suppose that you are importing documents with auto-numbering of documents, and each line of the source contains one document.

If you clear the Break on error check box, all correct documents will be imported first, and then you will review all errors at once and import the corrected records. The order in which the reference numbers are assigned to the imported documents will be different than in the situation if you import documents one by one and stop after each error.

If the order of record processing is not important, you can clear the Break on error check box.

A check box that indicates (if selected) that the system will stop processing records at the first error that occurs for a record that violates the target restrictions.

You specify this option for a particular execution of a scenario. That is, the selected value is discarded after each execution of the scenario or each refresh of the page.

A check box you select to validate the selected import scenario. The scenario processing emulates data import and is cancelled if an error occurs. If you want to save the imported data after successful validation, select the Save if data is valid check box.

You specify this option for a particular execution of a scenario. That is, the selected value is discarded after each execution of the scenario or each refresh of the page.

A check box you select to save the data if the import validation is successful. Clear the check box if you don’t want to save the data after import validation.

This option is available only when you select the Validate data (no saving) check box to switch to import validation mode.

You specify this option for a particular execution of a scenario. That is, the selected value is discarded after each execution of the scenario or each refresh of the page.

A check box that you select to not import the titles of the elements in the window.

You specify this option for a particular execution of a scenario. That is, the selected value is discarded after each execution of the scenario or each refresh of the page.

The name of the Visma Net window whose functionality will be used to perform data import.

You can select the screen name by finding its workspace, finding its section, and selecting the applicable form.

The type of synchronisation for the import scenario, which can be one of the following options:

Full

Select this option to perform import of all the data available in the source.

Incremental - all records

Select this option to perform partial import, including only the data in each record that has changed in the source.

Incremental - new only

Select this option to perform partial import, including only records that have appeared in the source since the previous import took place.

If the data is imported from a file data source, the Incremental - all records and Incremental - new only options provide the same result: Selecting either of these options makes the system import the data only if a new version of the source file is provided before import.

Displays the Visma Net 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.

The logical operation to apply to the value of the selected field; in some cases, the operation entails comparing it to the values specified for Value and Value 2.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 null

Returns True if the field value is null.

Is not null

Returns True if the field value is not null.

Does not contain

Returns True if the field value (string) does not contain the value specified in the Value field.

The logical operation to apply to the value of the selected field; in some cases, the operation entails comparing it to the values specified for Value and Value 2.

Typically, the following options are available: Equals, Does not equal, Is greater than, Is greater *than or equal to*, Is less than, Is less than or *equal to*, Is between, Contains, Ends *with*, Starts with, Is null, Is not *null*.

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

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

An automatically created file name showing the company ID and From/To period for the included attachments.

Example:

Company: 123456

Document type:

AR - Customer transactions,

AP - Supplier transactions,

GL- General ledger transactions, or

CA - Cash transactions

From period: 202301

To period: 202312

An automatically created file name showing the company ID and From/To period for the included attachments.

Example:

Company: 123456

Document type:

AR - Customer transactions,

AP - Supplier transactions,

GL- General ledger transactions, or

CA - Cash transactions

From period: 202301

To period: 202312