> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/releases/29.0.md). # 29.0 Changelog for Golden EDI version 29 that was released on 2026-09-24 ## Description Welcome to our latest release! Highlights of this release are * Full support for BC 29. * Improved handling of GEDI Profile updates on sales and purchase documents. * User experience improvements to GEDI Mapping Documents. * GEDI fields are now fully available on archived documents ### Why we made these changes **Full support for BC 29** The GEDI 29 release is fully compatible with BC 28 and is already available on Marketplace for BC 28. However, the release is BC 29-ready and will be the first official release for BC 29. **Improved handling of GEDI Profile uppdates** When a user selects a customer or vendor on a sales or purchase document, the system automatically applies the GEDI Profile from the customer or vendor card. If the user later changes the customer or vendor, there are cases where the user may want to control whether the system updates the profile automatically again. With this release, you can choose the behavior with the options Always (default), Never and Ask. **User experience improvements on GEDI Mapping Documents** The mapping document is one of the interfaces GEDI experts use most. It lets the user map data between different document formats (BC native and external). The mapping document lines are now non-editable when the status of the mapping document doesn't allow changes. This makes it clearer that the user must first reset the status of the document before making changes. In addition, the Value Type is now assigned automatically when you reference a table field. **GEDI fields fully availble on archived documents** Archived sales and purchase documents now inherit and display the relevant GEDI fields from the source document. This means archived documents can be used with all critical GEDI information intact. ### What this means for you **For Most Users**: No Action Required * Users and clients who want more control over how GEDI Profile updates are handled on sales and purchase documents can set the new options in GEDI Setup. ### For Partners and Integrations **If you have custom integrations using the Golden EDI API:** * The API contract version has been updated to version 3.3. ### **Changelog** **Golden EDI** * "GEDI Document Exchang ID" field has been extended to 50 characters. * Added the field "GEDI Invoice Allowed" to the Sales Header. * GEDI Backups can now also be triggered from the CIP side. * Added the field "GEDI Sync Item" to the Item table. * The GEDI mapping engine now allows more than 10 levels. * Improvements to Application Insights (logging). * Minor corrections and general improvements. **Extended Platform** * Minor corrections and general improvements. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.goldenedi.com/releases/29.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.