Enter the MBC connection settings using the details provided by the person responsible for your organisation's integration. Saving the settings requires administrator rights and an MBC integration configured for your customer account. Configure the connection in Spotilla's browser interface.
Open the settings and gather the required information
Open Settings → Integrations → Integrations. Click the name of the Mbc row in the list. MBC integration settings opens.
If the connection is missing from the list, contact your Spotilla representative about setting it up. See also the prerequisites for setting up an integration and checking its status.
Before you begin, confirm the authentication method, its credentials and the URLs for all endpoints. You will also need the Spotilla base folder and device card, as well as MBC's location codes, work order types and work order states. Use values confirmed by the person responsible for the integration.
Select the authentication method
In the Authentication type field, select cloud for a Microsoft cloud connection or ntlm for a local server connection. The form displays the fields for the selected method.
If you select cloud, complete all three fields in the Cloud authentication section:
- Client ID: the application identifier used for authentication.
- Client secret: the application's authentication secret.
- Client UUID: the tenant identifier for the Microsoft environment, used to construct the authentication URL.
If you select ntlm, complete Workstation, Password, Customer name and Username in the NTLM authentication section. In this section, Customer name refers to the NTLM domain. This is different from the read-only Spotilla customer account name shown later under the same label.
Changing the authentication method clears the other method's credentials when you save: cloud clears the NTLM fields, and ntlm clears the cloud authentication fields. If you switch back later, enter that method's details again.
Complete the basic configuration and lists
In Basic Configuration Section, select Device card and Base folder from the existing Spotilla options. Both are required. Customer name in this section is a read-only identifier for the customer account.
Confirm with the person responsible for the integration that the base folder and device card are suitable. Before changing the configuration, verify their exact effect on the creation of customer folders, the placement of Spots and subsequent changes to previously transferred data for the connection in use.
In the Inventory Configuration section, add MBC's Location code values. In Work order Section, add Types of Work Orders and Work Order States. The form requires at least one location code, one type and one state.
- Click Add below the relevant list.
- Enter a value in the field that opens and click its Save button. The value is added to the list on the form.
- Repeat this for each required value. You can edit a value cell in the list or delete a row using its trash icon.
The lists' own Save buttons and trash icons only change the data in the open form. Save the entire configuration separately at the bottom of the form. Deleting a settings row does not itself delete previously transferred data.
Agree on the location code, type and state filters with the person responsible for the integration. Verify through an actual transfer which data the selected values bring in and how multiple filters are applied together.
Enter the endpoint URLs
In the ODataV4 Objects Endpoints section, complete all the following fields using the URLs provided by the person responsible for the integration. The field names are in English even in the Finnish interface.
- Customers and Ship to Customers: endpoints for customer and ship-to customer data.
- Service Items: the endpoint for service items.
- ServiceOrders and Service Order Lines: endpoints for work orders and their lines.
- Warehouse Bin List, Warehouse Products and Warehouse Product By Categories: endpoints for warehouse bin and product data.
- Resources and ResourceGroups: endpoints for resources and resource groups.
- Authentication Endpoint: the authentication endpoint.
All endpoint fields are required for both authentication methods. The form accepting a completed field does not confirm that the URL works or that the credentials have the necessary permissions in MBC.
Check the invoicing option and integration status
The Tasks to Sales Invoice settings field defaults to Only tasks with task number create invoices if no previous selection exists. The other option is All tasks create invoices. This selection concerns task invoicing; work order types and states are separate settings.
There is an inconsistency in how the invoicing selection is handled: the selection saved on the form and the invoicing setting saved for the Spotilla customer account may differ. In particular, selecting the option for tasks with task numbers cannot be relied on to restrict invoicing based solely on the form selection. Confirm the actual effect on invoicing with Spotilla support and check the result of an agreed test task before production use.
In the Integration status field, select In use when you want to activate the connection. Saving creates an integration user if needed or uses the existing integration user.
Not in use disables the integration's Spotilla user credentials and permission to write to the log. Successfully saving the deactivation deletes the integration user. This deactivates the connection: it does not delete previously imported customers, Spots or work orders, or roll back transferred data.
Save and verify the result
Click the Save button at the bottom of the entire form. The required details and lists are also needed when the status is set to Not in use. Cancel closes the form without submitting changes.
If saving fails, check the message and any missing fields. After the success message, reopen the settings for the Mbc row and check the authentication method, status, list values and other settings.
The active status in the integration list is based on the existence of the integration user. It does not prove that the connection or an individual data transfer has succeeded. Monitor the agreed first transfer on the Settings → Integrations → Changelog tab and compare the transferred data in Spotilla and MBC. Also check how the data is mapped and any invoicing result.
If the result is missing or incorrect, record the event time, target and error description for the person responsible for the integration or for support. See also investigating an integration error using the log.