Microsoft Dynamics 365 Business Central / NAV Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.
See TIBCO Scribe® Online Connector For Microsoft Dynamics 365 Business Central / NAV for more information.
Note: To access any changes to metadata support, such as new operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata.
Version 1.6.5
Released March 28, 2022.
New And Noteworthy
- Added support for OData V7.9 libraries.
- Added support for Collections.
- Added support for Hierarchical relationships, such as grandparent, parent, grandchild relationships.
- Added support for Client Secret Authentication method.
- Added Send operation functionality which is used to make API calls to the API. The Send operation supports the Request entity used to build the calls to the API.
Changes In Functionality
Microsoft Dynamics 365 Business Central / NAV is retiring support for OData V3. Based on that change by Microsoft, the TIBCO Scribe® Online Connector For Microsoft Dynamics NAV will no longer support OData V3.
Best practice is to configure one or more new Connections using one or both of the two OData V4 Service URL endpoint options. The OData Service URL for the REST version of the API ends in Production/api/v1.0. The OData V4 Service URL ends in /Production/ODataV4/ . Reassign the Connections used in your Maps to the new Connection or Connections you configured. The metadata returned by the OData V4 endpoints may not be exactly the same as the OData V3 metadata and could require extensive edits to your Maps. (SCMSNAV-204, SCMSNAV-325)
Net Change uses Date and DateTime fields to locate new and updated records and stores the Date and DateTime value of the last record processed. The next time the Solution runs, the Query Block requests records with:
- A Date that is greater than the Date value of the last record processed.
-
A DateTime that is greater than or equal to the DateTime value of the last record processed.
Dynamics 365 Business Central / NAV timestamps in datetime values are always set to midnight or 00:00:00. When using Net Change with this type of datetime fields, running a Solution another time on the same day causes new and updated records for that day to be processed again. For example, if you run a Solution on 10/15/2020 at 10 AM and the last record processed has a date of 10/15/2020 00:00:00:, when the Solution runs again on 10/15/2020 at 9 PM, any records updated or created before 10 AM are processed again because Net Change is requesting records with a datetime greater than or equal to 10/15/2020 at midnight.
Best practice is to schedule the Solution to run once a day after all records have been created or modified for the day to process all of the records for that day. For example, if your business day ends at 6 PM, schedule the Solution to run after 6 PM to ensure all records for the day are processed only once.
Closed Issues
SCMSNAV-323
Attempting to use the Update/Insert block in a Map generates errors similar to the following on the Block Errors and Warnings tab:
Operation 'Update" is not an available Update operation for Source Entity 'Customers'.
SCMSNAV-9
When using Net Change with datetime fields set to midnight or 00:00:00, running a Solution another time on the same day causes new and updated records for that day to be skipped.
Known Issues
SCMSNAV-738
Summary: If your Company Name or any other Microsoft Dynamics 365 Business Central / NAV data contains an apostrophe or single quote ('), the connector generates an error. Errors similar to the following are generated when the Company Name used in the Connection dialog contains an apostrophe ('):
The following error has occurred in the Dynamics NAV Connector: Resource not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
Workaround: Use a second apostrophe or single quote (') as an escape character. Example: If the Company Name is Bob's Company, enter Bob''s Company. Use the same approach for any data containing an apostrophe or single quote.
SCMSNAV-678
Summary: In some cases the connector cannot parse or display all of the errors returned when a target operation fails. Instead the following error is returned: Stream was not readable. (Case # 01807499, 01866987, 01879058, 01882445, 01921837, 01931029, 01941068, 02046463, 02051707, 02055721, 02076008, 02076044)
Workaround: Send the same request to the Microsoft Dynamics 365 Business Central / NAV API using POSTMAN to see the actual error.
SCMSNAV-501
Summary: Using the Query Preview tab when querying the Attachment entity generates errors similar to the following:
ERROR: Exception Type : InvalidExecuteQueryException
Message: The following error has occurred in the Dynamics NAV Connector: Bad Request. The request could not be understood by the server
Workaround: The Attachment entity is not fully supported by the API. The best practice is not to use it as a source or target entity.
SCMSNAV-10
Summary: In some cases, entities that return a large amount of data do not display in the Query Block Properties Preview tab nor in Debug. (Case # 01852928)
Workaround: Depending on the entity, using a filter may resolve this issue.
Version 1.5.1
Released March 29, 2021
New And Noteworthy
There are no new features in this release.
Changes In Functionality
Microsoft Dynamics 365 Business Central / NAV is retiring support for OData V3. Best practice is to configure one or more new Connections using one or both of the two OData V4 Service URL endpoint options. The OData Service URL for the REST version of the API ends in Production/api/v1.0. The OData V4 Service URL ends in /Production/ODataV4/ . Reassign the Connections used in your Maps to the new Connection or Connections you configured. The metadata returned by the OData V4 endpoints may not be exactly the same as the OData V3 metadata and could require extensive edits to your Maps.
If you choose to update the OData Service URL in your existing Connections, you must Test the Connection and save it. After the updated Connection is saved, reset metadata for the updated Connection to retrieve metadata for the new URL. Note that you may need to edit your Maps to accommodate the changes to the metadata.
Entities returned using the OData V4 service URL contain Date fields that are strings instead of DateTime fields. The Connector converts the Date string fields into DateTime fields where the time defaults to midnight. This causes some records to be reprocessed the next time the Map runs. Your Maps should be designed to check for duplicate records. You may want to consider using the OData Service URL for the REST version of the API, which has more support for DateTime fields. (SCMSNAV-204)
When moving from OData v3 to OData v4, note that the UpdateMerge block is not supported in OData v4 and must be changed to UpdatePatch in your Maps.
Closed Issues
SCMSNAV-203
When a Create Block creates a new record, values for unmapped fields are returned and can be used in subsequent operations, such as an ID generated for the new record. (Case # 01905172)
Version 1.4.1
Released October 19, 2020.
New And Noteworthy
- Added support for the v1.0 REST API to access OData 4 endpoints. The OData Service URL for the REST version of the API ends in Production/api/v1.0. The existing OData Service URL ends in either /Production/ODataV4/ or /Production/ODataV3/ depending on which version of OData you are using. (SCMSNAV-49, SCMSNAV-177)
- Improved retry logic to minimize the impact of API rate limiting. (SCMSNAV-51)
- Improved paging when returning large sets of data to prevent API timeouts. (SCMSNAV-11)
Changes In Functionality
Microsoft Dynamics 365 Business Central / NAV is deprecating support for OData V3 in 2021. Best practice is to configure a new Connection using one of the two OData V4 options, and then update your Maps as needed. The metadata returned by the OData V4 endpoints may not be exactly the same as the OData V3 and could require extensive edits to your Maps. (SCMSNAV-177)
Closed Issues
SCMSNAV-176
Bad syntax errors were generated when attempting to query using a filter value that contained an apostrophe ('). (Case # 01864222)
Version 1.3.0
Released October 15, 2018.
New And Noteworthy
- Added support for OData V4 endpoint. (69749)
- Validated the Connector against Microsoft Dynamics 365 Business Central.
Closed Issues
56304 / 57487
Microsoft Dynamics 365 Business Central / NAV returned errors similar to the error shown below, when TIBCO Scribe® Online attempted to execute Create Purchase_InvoicePurchLines operations. (Case # 62562, 62988)
Error description: Operation failed. Label: Create Purchase_InvoicePurchLines, Name: Purchase_InvoicePurchLinesCreate, Message: Error Code: Description: Sorry, we just updated this page. Reopen it, and try again.: Error in calling Operation Create
Version 1.2.0
Released October 27, 2017.
New And Noteworthy
There are no new features in this release.
Closed Issues
36000 / 36425
Updated the Connector to include milliseconds in the datetime field used when filtering for new and changed records to prevent reprocessing records that have already been processed. (Case # 38615)
53686
Enhanced retry logic to prevent timeouts that caused a Connection forcibly closed error. (Case # 58355)
April 13, 2016
New And Noteworthy
There are no new features in this release.
Change In Functionality
Relationships are no longer supported.
Closed Issues
There are no Closed Issues in this release.
February 1, 2016
New And Noteworthy
Added support for the following operations:
- Query
- Create
- Delete
- Update
- Update/Insert
- UpdateMerge
- UpdateReplace
Closed Issues
There are no Closed Issues in this release.
