John Deere DBS 2026 Releases

• JD26R1 Release Note (2026/01/30)
• JD26R2 Release Note (2026/03/30)
• JD26R3 Release Note (2026/05/31)

JD26R1 Release Note

2026/01/30

• Bugfixes
  • [#30116] Issue related to creating calculation forecasts from integration records
  • [#30154] Issue related to JDLink and storing JDLink logs
  • [#30310] Issue related to random line breaks in machine comments
  • [#30390] Issue related to modifying service items with inactive service item models
  • [#30459] Issue related to revaluation journal lines and tracking specs
  • [#30579] Issue related to GPC validation in purchase orders
  • [#30816] Issue related to maximum character length of trade-in import IDs
  • [#31098] Issue related to applying standard job lines for items
• New Developments
  • [#28722] UPDATE: JD Warranty Interface APIs migrated from SOAP to REST
  • [#29999] OSI logic updated
  • [#30201] Sorting of CRM Customer Order configurations improved

Bugfixes

[#30116] Issue related to creating calculation forecasts from integration records

When receiving a customer order integration record from John Deere CRM, in which multiple machines have no DBS machine ID, a calculation forecast could not be created due to the error message that the record in the Machine table already exists. This issue was fixed.

[#30154] Issue related to JDLink and storing JDLink logs

The JDLink log was not correctly written as the operating hour update failed from time to time. This issue was fixed. Now, checks are in place, so that updates are not failing during the JDLink update process.

[#30310] Issue related to random line breaks in machine comments

When opening the comments of John Deere equipment in Notepad, line breaks occurred at wrong positions. This issue was fixed.

[#30390] Issue related to modifying service items with inactive service item models

It was not possible to modify a service item with an inactive service item model. This issue was fixed.

[#30459] Issue related to revaluation journal lines and tracking specs

There was the issue that tracking specs were written in items, although revaluation journal lines were created. This issue was due to synchronizing the serial number to tracking specs. This issue was fixed.

[#30579] Issue related to GPC validation in purchase orders

The unnecessary GPC validation led to issues when creating a purchase order from an offer. This issue was fixed by removing the GPC validation from purchase orders.

[#30816] Issue related to maximum character length of trade-in import IDs

The allowed string length of import IDs for trade-ins was too short, so that customer order import issues occurred. This issue was fixed by using the crmIdentifier field when data was retrieved from John Deere CRM.

[#31098] Issue related to applying standard job lines for items

When a standard job line of Type = Item had the Vendor Item No. value assigned, which was changed on the related item record, this line was not added to the service line in the service order anymore. This issue was fixed.

New Developments

[#28722] UPDATE: JD Warranty Interface APIs migrated from SOAP to REST

In this feature, the Warranty Interface API migration from SOAP (codeunit 5446233) to REST (codeunit 5446276) was finalized. With the new API, John Deere DBS will benefit from improved performance, scalability, and simplified integration for modern web and mobile applications. Also, the internal John Deere warranty types can now be submitted.

Important

On the newly created JD Warranty Setup Rest API page, set up the REST URL in the Base URL field which is the following:

• Cert: https://jdws-api-sandbox.deere.com/digcust/wy/cert/
• Prod: https://warrantyext-api-prod.deere.com/digcust/wy/

Additionally, please and add the Okta Interface Code value, and activate the interface by selecting the Active checkbox.

Also a new mapping was implemented in the John Deere Warranty Worktypes table which needs to be set up as follows (the Work Type Code is dealer-specific):

[#29999] OSI logic updated

In this feature, the logic of the OrderStatus Interface (OSI) was updated as the new OSI JSON file from John Deere contains all required processing data. The Build & Price Interface data is not needed anymore and was thus removed from the OSI processes.

The CRM Equipment Interface does now fill the Presold Date and Retail Sold Date values in the Service Item table to fill the presoldDate and retailSoldDate values in the JSON file.

When a service item component was attached, the corresponding line is sent to John Deere CRM without a price.

[#30201] Sorting of CRM Customer Order configurations improved

In this feature, the sorting of CRM configurations was improved. When creating a new offer from a CRM Customer Order integration record, the calc. configurations are now added sorted in ascending order. This enhances the available data in John Deere DBS, as the calc. configurations are created with the same sorting as the CRM data.

JD26R2 Release Note

2026/03/30

• Bugfixes
  • [#31548] Issue related to estimated parts price calculation
  • [#31566] Issue related to skipping DPM transfer in picklists and shopping baskets
  • [#32042] Issue related to setting jobs to reviewed
  • [#32280] Issue related to overwritten lines during B&P import
• New Developments
  • [#30061] CRM Integration export scope extended
  • [#31194] Automatic sequence nos. for attached components
  • [#31869] Profile ID synchronization removed from CDI
  • [#32109] Material code mapping for Warranty REST API implemented

Bugfixes

[#31548] Issue related to estimated parts price calculation

The Estimated Parts Price (LCY) field was not calculated correctly in standard service code lines. This issue was fixed.

[#31566] Issue related to skipping DPM transfer in picklists and shopping baskets

When selecting the Skip DPM Transfer checkbox on the Customer Card and then importing a Parts ADVISOR picklist or a shopping basket, the Skip DPM Transfer checkbox in the resulting lines was cleared. This issue was fixed.

[#32042] Issue related to setting jobs to reviewed

When trying to set jobs to reviewed in the Service Order Card via the Home > Set Jobs to Reviewed button, an error message was displayed referring to outdated information. This issue was fixed.

[#32280] Issue related to overwritten lines during B&P import

When importing a Build & Price file, existing calculation lines were overwritten. This issue was fixed.

New Developments

[#30061] CRM Integration export scope extended

In this feature, the following enhancements were introduced to improve data integrity and ensure seamless integration between John Deere CRM and John Deere DBS:

• The read-only PLI ID, JD Order Comment, and JD Order Status fields were added to the Vendor FastTab of the Service Item Card to store the Product Line Item (PLI) identifier received from the Customer Order Interface (COI) as well as related purchase order comments and status. This addition ensures that CRM customer orders are properly closed without data corruption, and it supports stable data exchange between systems.
• The Equipment Interface (EI) export was extended to include the following OSI fields, which are mapped to the JSON export file sent to John Deere CRM, required for CRM processes and reporting: PLI ID, JD Order Comment, and JD Order Status.

[#31194] Automatic sequence nos. for attached components

Service item component lines with Status = Attached are now automatically set to Sequence No. = 999999 upon inserting them, so that the component structure becomes clearer and easier to read for users. The Sequence No. value can be manually adjusted, if needed.

[#31869] Profile ID synchronization removed from CDI

In this feature, the profileID JSON tag was removed from Customer Data Interface (CDI) processes for customers and contacts, so that it is not synchronized anymore.

[#32109] Material code mapping for Warranty REST API implemented

In this feature, the mapping of the Other Credit - Material Code table was implemented for the new REST API, so that users can switch between the SOAP and REST APIs without adjusting existing warranty claims.

JD26R3 Release Note

2026/05/31

• Bugfixes
  • [#32685] Issue related to missing product hierarchy name in CRM Equipment Interface
  • [#32709] Issue related to product hierarchy not being filled completely in trade-ins
  • [#32957] Issue related to missing VAT amount on additional lines in posted trade-in sales credit memos
• New Developments
  • [#32394] Sending UOMs in warranty claims improved
  • [#32790] JDLink functionality reworked for higher reliability
  • [#32891] Manual Okta token input for Warranty REST API implemented
  • [#33260] JDPrism export optimized for coordination IDs

Bugfixes

[#32685] Issue related to missing product hierarchy name in CRM Equipment Interface

When synchronizing machine data via the CRM Equipment Interface, the product hierarchy attributes were missing. When manually creating a machine, the information was automatically filled properly. This issue was fixed.

[#32709] Issue related to product hierarchy not being filled completely in trade-ins

When creating a trade-in from a CRM customer order for a machine already existing in John Deere DBS, only the Model value was filled for the product hierarchy (Brand, Family, and Series were missing) in the trade-in record. This issue was fixed.

[#32957] Issue related to missing VAT amount on additional lines in posted trade-in sales credit memos

When posting a trade-in order with multiple lines, the VAT amount was missing on the second (and subsequent) line(s) in the resulting posted sales credit memo. This issue was fixed.

New Developments

[#32394] Sending UOMs in warranty claims improved

In this feature, the language code for sending units of measure (UOM) in warranty claims to John Deere was set to English, so that the information can be properly read by JD WASP. The UOMs in John Deere DBS records remain in the current language.

[#32790] JDLink functionality reworked for higher reliability

In this feature, the JDLink functionality was reworked to improve manual updates of operating hours and location data. The following was changed:

• The MyJohnDeere Equipment URI value in the JD Link FastTab of the John Deere Setup page was updated.
• The organization loop to request organization machines and equipment was removed to reduce complexity. The same functionality is already provided by John Deere.
• The Principal Id value on the Service Item Card is now filled properly.

[#32891] Manual Okta token input for Warranty REST API implemented

In this feature, the option to manually input an Okta authentication token was implemented. To manually enter tokens, select the JD Warranty (Rest) OKTA User manual token checkbox in the John Deere User Setup table. The corresponding dialog is automatically called when the token is expired or missing.

This provides an alternative authentication method for the Warranty REST API when automated token retrieval is not available. To keep the tokens refreshing automatically, enter the number of minutes before which the token should be refreshed in the Refresh Access Token before Expiration (Minutes) field on the JD Warranty Setup Rest API page.

[#33260] JDPrism export optimized for coordination IDs

In this feature, the export via DPMEXT of the JD Prism Coordination IDs provided by the JDPrism Interface has been improved, so that up to 800 JDPrism Coordination IDs per day can be exported. It will be sufficient for the future DPMEXT file creations and solves the case that dur to the text length for the list of JDPrism Coordination IDs only up to 100 records were consumed on a daily basis.