# Implementation Academy Learn how to install and configure Golden EDI for Microsoft Dynamics 365 Business Central ## Welcome to Implementation Academy This is where you as a key user or application consultant will be able to learn how to install and configure Golden EDI in Business Central. Supported by our Guides, Courses and Core Concept you will be able to learn it all at your own pace. ## The knowledge collection ### Core Concepts {% content-ref url="/spaces/Fe4Q6J1fzsyYoa0sjFct" %} [Core Concepts](https://docs.goldenedi.com/core-concepts/) {% endcontent-ref %} In Core Concepts you will find the necessary facts to understand how the Golden EDI apps and services work. All about the required background settings and how they all together create and affect the EDI-flows. ### Courses {% content-ref url="/spaces/xwncnNzHcS0rO9lJ3q5R" %} [Courses](https://docs.goldenedi.com/courses/) {% endcontent-ref %} In Courses you find lessons that will teach you how to implement Golden EDI. The Beginner Courses will take you through installation of the Golden EDI App, how to import prepacked 'GEDI Setups' and give you the basic knowledge about 'GEDI Message Queue', standard 'GEDI Message Codes' and standard 'GEDI Mapping Documents'. The Configuration Courses will give you a deeper understanding about all the configurable GEDI settings. After this course you will be able to configure new 'GEDI Profiles', edit which event that shall trigger 'GEDI-messages' and what 'GEDI-mapping documents' they shall use. The Mapping Courses will give you in depth knowledge about the mapping documents. The core that creates the actual content in the outgoing 'GEDI Messages' and interpret and consume the information received in incoming 'GEDI-messages'. After this course you will be able to edit existing 'GEDI-mapping documents' and even create new. ### Guides {% content-ref url="/spaces/zhgbu1mdtStXCa9HahV2" %} [Guides](https://docs.goldenedi.com/guides/) {% endcontent-ref %} In Guides you find step by step manuals for installing the Golden EDI App and initiating our 'GEDI Setups', as well as other useful guides. # Useful Links Appsource for **Dynamics 365 Business Central** {% embed url="" %} Download the Golden EDI standard App from Microsoft Appsource {% endembed %} {% embed url="" %} Download the Golden EDI Extended Platform App from Microsoft Appsource {% endembed %} ## Cloud {% embed url="" %} ## Links {% embed url="" %} For more information about Golden EDI and what we do, please visit {% endembed %} {% embed url="" %} If any questions, please visit our support section on our website. {% endembed %} {% embed url="" %} To get in touch visit our Contact area at our website. {% endembed %} # Core Concepts Collection Core Concepts for Golden EDI for Microsoft Dynamics 365 Business Central {% content-ref url="/spaces/CnajZpb6jyP8d1VA5elK" %} [Standard App Core Concepts](https://docs.goldenedi.com/standard-app-core-concepts/) {% endcontent-ref %} {% content-ref url="/spaces/XNBbIIhQSyozDaF9mFe2" %} [Broken mention](broken://spaces/XNBbIIhQSyozDaF9mFe2) {% endcontent-ref %} {% content-ref url="/spaces/vAc2to3RKEGaaTc8CTmA" %} [Broken mention](broken://spaces/vAc2to3RKEGaaTc8CTmA) {% endcontent-ref %} # Intro Core Concepts for Golden EDI Standard App for Microsoft Dynamics 365 Business Central ![Golden EDI Standard App Core Concepts](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FJvc1zK7LjaQTp9bwcNNf%2FCore%20Concepts.png?alt=media\&token=286963e3-767d-4138-896c-7d7bbb8325f4) ## Golden EDI Standard App The Golden EDI Standard App for Business Central has functions for importing, exporting and controlling data in a configurable framework without coding needed. Many standard functionalities are ready to use "out of the box". Golden EDI is used to transfer data between Business Central and external parties, other applications or intercompanies. Golden EDI is a 2-layered solution for EDI; The Standard App handles processes inside Business Central, the Cloud Integration Platform (CIP) handles the communication between sender and receiver. A Work Item Id for each transaction is the link between the two layers. Golden EDI can also be used to transfer data between different tables inside the same Business Central company. This can be useful when Business Central is integrated with other applications or for Partner Apps where populating custom tables with certain data is needed. A few examples of integration flows where Golden EDI can be used: E-Invoices via Value Added Network (VAN) ![E-Invoices via VAN](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FGaKJAnMg8uFEMFGqEQdp%2FInvoices.png?alt=media\&token=ab7ed7a0-f6e3-43ec-9012-7403a84705ed) Order to Cash (Sales Order Import to Invoice Export) ![Order to Cash](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FdzYYHHg7TQP4gNMIDjUG%2FOrder%20to%20Invoice.png?alt=media\&token=1e87648e-7f31-4c98-97a5-4aa7f2c755d4) Webshop integration with 3PL integration ![Web shop integration with 3PL integration (Dotted lines not handled by Golden EDI)](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FDiTo3jEY06xH006209U5%2FWebshop%20order%20with%203PL.png?alt=media\&token=c0a680a3-04a6-4ee7-a7e9-2ac370cf37af) Intercompany Sales to Purhase ![Intercompany Sales to Purchase](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2Fb3JQJDhszcCAaIVcKov1%2FIC%20Sales%20-%20Purchase%20-%20Sales.png?alt=media\&token=b26e67f6-6430-47c2-989e-64c2b52593a0) Intercompany Masterdata update ![Intercompany Masterdata update](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FP92uNnv4FBSMcj2vJ4Yw%2FMasterdata.png?alt=media\&token=2752f361-3e97-4b96-84e1-77c6af57870e) {% embed url="" %} Golden EDI Standard App for Microsoft Dynamics 365 Business Central on Appsource {% endembed %} # Cloud Integration Platform "Cloud Integration Platform manages communications with other parties" ![The Cloud Integration Platform](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FcTKYrPpw70ZXJKfguafR%2FCC%20The%20CIP.png?alt=media\&token=57be263b-a784-4757-b5be-d4cb620a808c) ## Introduction Before we go into the details of the Standard App for Business Central, we will go through some basics on how the Cloud Integration Platform (CIP) manages communications with other parties. The CIP is an online cloud solution on Microsoft Azure. ## CIP Connections In the CIP, connections between different parties are configured. The CIP Connection holds information about which Business Central company it should connect to, and what other party it should integrate with. It can be a direct connection, for example between your Business Central company and 1 of your customers. Or it can be a connection to a Value Added Network (VAN), were multiple parties can be integrated through the same connection. The connection also holds information on which communication protocol that should be used to communicate with the other party. For example FTP, API, AS2 etc. Communication with the Business Central company is usually via Web Service SOAP, but could also be via other means. Each CIP connection has a Connection ID and a API key, this is linked in the Standard App to a 'GEDI Profile'. More on the 'GEDI profile' later. ## CIP Translators Communication between the Standard App and the CIP is always done via a internal JSON format. A CIP Translator is a code script to convert between the internal JSON format and the format that the other party can handle, for example PEPPOL, EDIFACT, X12, XML etc. In the CIP translator it is defined which direction it converts (incoming/outgoing), which format it converts to and from (PEPPOL, EDIFCAT etc) and which Message Document Type it converts (Order, Invoice, DespatchAdvice etc). There are general translators that follow the standards for the format, and there can be specific translators that is custom made for parties with more specific demands and setups. In the CIP Connection it is defined which directions, document types and translators that are allowed to be used for that CIP Connection. ## CIP Work Items A transaction in the CIP is called a Work Item, usually this is an incoming EDI file from an other party or it is an outgoing message from the Standard App. It is then processed and converted as part of several steps. When the CIP reads or writes Work Items to and from the Standard App, the Work Item ID is updated and viewable inside Business Central. ## References For more details about the CIP, see bellow page on Core Concepts for Cloud Integration Platform. {% content-ref url="/spaces/vAc2to3RKEGaaTc8CTmA" %} [Broken mention](broken://spaces/vAc2to3RKEGaaTc8CTmA) {% endcontent-ref %} # GEDI Messages Queue "A 'GEDI Message', is something that willl be or has been processed" ![GEDI Message Queue](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FlIQA9sapJVXrCzGustJ9%2FCC%20Message%20Queue.png?alt=media\&token=e67841e8-de16-447e-bef1-120730f1a23b) ## Introduction In the 'GEDI Message Queue' page view in Business Central you will find 'GEDI Messages'. A 'GEDI Message', is something that will be or has been processed within the Standard App. There are different types of 'GEDI Messages', for example exports, imports, control functions, emails, status updates and much more. The exact function of each 'GEDI Message' is defined by a 'GEDI Message Code'. In the 'GEDI Message Queue' page view it is possible to manually process, reprocess or run 'GEDI Messages' for testing purpose. 'GEDI Messages' can be automatically deleted by a Job Queue Entry. This clean up is making sure that the 'GEDI Message Queue' doesn't store too much data. This is to make sure that we don't have negative impact on performance over time. 'CIP Work Items' are read or written to the Standard App as 'GEDI Messages' holding a unique 'Work Item' ID. The 'CIP Work Item' ID acts as a link between the two layers; Business Central and the CIP. # GEDI Setup Catalog "A 'GEDI Setup' is an XML file containing a complete GEDI configuration package" ![GEDI Setup Catalog](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2Fwx0Vk2BxLtNKJAvzF2e4%2FCC%20Setup%20Catalog.png?alt=media\&token=254c379f-af64-44c8-acc3-4b2149daf26a) ## Introduction In the 'GEDI Setup Catalog' page view in Business Central you will find 'GEDI Setups'. A 'GEDI Setup' is an XML file containing a complete GEDI configuration package of the Standard App. Using the 'GEDI setups' is a powerful and efficient way to import and export GEDI configurations on company level in Business Central. Some standard 'GEDI Setups' are uploaded to the CIP and can be downloaded directly via the interface. Other 'GEDI Setups' are xml files that are created from other Business Central environments and can be uploaded into the App manually. It is possible to save current GEDI configurations in the App as a new 'GEDI Setup', for backup purposes or for moving the GEDI configurations between different Business Central companies. This means that moving a setup from a test environment to a production environment can be done smoothly using 'GEDI Setups'. It is possible to completely delete all GEDI configurations in a Business Central company if you want to start anew. Doing that will automatically create a back up. {% hint style="danger" %} It's advised to always create a 'GEDI Setup' backup before beginning any new changes after go-live. This way original configuration can always be restored. {% endhint %} ![Example of what the 'GEDI Setup Catalog' can look like. ](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2Fg3uCwtgP56kdyz3caLh0%2Fbild.png?alt=media\&token=92d7e7d5-73d1-423f-91ac-1231b33d8218) ## Modular and Complete Setups 'GEDI Setups' can be either modular or complete GEDI configurations, depending on how they were designed. When importing 'GEDI Setups' after each other any new configurations will be added on top, and if any conflicts should occur the latest setup imported will overwrite existing GEDI configuration. Modular 'GEDI Setups' are usually those that are uploaded to the CIP, and includes Prepacked setups and template setups. The Modular 'GEDI Setups' more strictly follow standard practices to make them compatible with each other. A Complete 'GEDI Setup' are usually a copy of a Business Central Company GEDI configurations. {% hint style="danger" %} Never import a 'GEDI Setup' if you are not sure what its purpose is, you always run the risk of overwriting existing GEDI configurations! {% endhint %} ## GEDI Setup concepts 'GEDI Setups' can be divided into some different concepts; * **Prepacked:** Usually modular, and should work "out of the box". Almost no additional GEDI configurations should be needed to start using the 'GEDI Setup' in production. These are in general terms easier to document, as every installation is more or less the same. 'Freemium' and 'Basic Invoice' are examples of Prepacked 'GEDI Setups'. * **Template:** Usually modular, and contains a lot of GEDI configurations were most of it is expected to be relevant. Some templates are closer to prepacked, and some are more generic. These are harder to document, as every installation will have different needs for additional GEDI configurations. 'Advanced Invoice' and 'Order-to-Cash' are examples of Template 'GEDI Setups'. * **Addon:** Usually modular, lightweight 'GEDI Setups' dependent on other 'GEDI Setups'. Used for commonly added features that are not included in the main 'GEDI Setup'. * **Demo:** Usually complete, and contains GEDI configurations to easily setup a demonstration of a function. These are not meant to be installed in Production environments, and should only be used in sandboxes or other test environments. * **Company Copy:** Always complete, intended to move all GEDI configurations from one company to another or to be used as a backup. # GEDI Profiles "A 'GEDI Profile' is the key to which processes you want to activate" ![GEDI Profiles](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2F2SU7QVXxtsrrVKupPi6M%2FCC%20Profiles.png?alt=media\&token=35552a61-b924-40ca-a81a-f720dad754f9) ## Introduction In the 'GEDI Profile' page view in Business Central you will find 'GEDI Profiles'. A 'GEDI Profile' is the key to which processes you want to activate in the Standard App, and what exact GEDI configurations will be used. A 'GEDI Profile' often refers to a 'CIP Connection', but not always. The 'CIP Connection' can be used for a "1 to 1 connection" for example between the Business Central company and one specific customer. Or it can be a "1 to many connection" to a Value Added Network (VAN) where the Business Central company reach multiple recipients/senders. 'GEDI Profiles' used only for Standard App internal functions don't need a 'CIP Connection'. Sometimes a 'GEDI profile' both use a 'CIP connection' and Standard App internal functions. Parties such as customers or vendors, that the Business Central company is going to integrate with, needs to have a 'GEDI Profile' set in the card details. That 'GEDI Profile' will then be inherited down to each transaction related to that party, for example orders and invoices. Sometimes within the same 'CIP Connections', there are different variations that is needed to support different scenarios. In this case multiple 'GEDI Profiles' can be configured against the same 'CIP Connection', but they will have different 'GEDI Message Setups'. For example when you have more than one method of delivering invoices or if the EDI-Invoices needs a variation in the content depending on the recipients. One of the most common scenario is the need of different banking details for different recipients within the same VAN 'CIP Connection'. ## GEDI Profile concepts 'GEDI Profiles' can be divided into some different concepts; * **CIP Connection Profiles:** Profiles with a 'CIP Connection' allows the CIP to read and write 'GEDI Messages' to that 'GEDI Profile'. This is the standard scenario for EDI. * **Internal profiles:** Profiles without a 'CIP connection' can be used for Business Central internal functions. For example, a PDF Invoice 'GEDI Profile' automates standard Business Central e-mail sending with PDF. In this case there is no need to integrate with the CIP. * **CIP Generic profile:** The 'GEDI Profile' 'INTERNAL' is a default profile to be used with the CIP for integrating general functions. The 'CIP Connection' ID for this profile is always 'GEDI-INTERNAL'. The 'GEDI Profile' 'INTERNAL' is for example used when downloading 'GEDI Setups' from the CIP. # GEDI Message Codes "A 'GEDI Message Code', is a definition of a specific function that a 'GEDI Message' will execute" ![GEDI Message Codes](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FCrgN4OMf9Qtj4Ei0NNO0%2FCC%20Message%20Codes.png?alt=media\&token=77fee627-690d-4335-bf76-64078253d856) ## Introduction In the 'GEDI Message Codes' page view in Business Central you will find 'GEDI Message Codes'. A 'GEDI Message Code', is a definition of a specific function that a 'GEDI Message' will execute. Each unique function has a corresponding unique 'GEDI Message Code'. For example Importing an EDI order is one 'GEDI Message Code', exporting an EDI Invoice is another. Often 'GEDI Message Codes' comes in a pair of two; one request and one execution. The request is created in the 'GEDI Message Queue' triggered by an event in Business Central. When that request is later processed, the function is actually executed. For example, information is extracted and inserted as 'GEDI message lines' or a control process is executed. After execution, a second 'GEDI Message' on another 'GEDI Message Code' is created for the result. This way the event that puts 'GEDI Messages' in the 'GEDI Message Queue' are separated from the execution of the actual function. This allows batch processing via a Job Queue running in the background, instead of delaying the user experience. For each 'GEDI Message Code', you can define a 'GEDI Status' that will be created. This will then update the processed record with the latest status. On the 'GEDI Message code' you can define a number of days in the field "Delete in Queue Days Back" deciding how long 'GEDI Messages' should be saved in the 'GEDI Message Queue'. A Job Queue Entry will handle the deletion of entries past due. ![Example of what the 'GEDI Message Codes' table can look like](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2Fvnjyxg0z64MEGEJuu390%2Fbild.png?alt=media\&token=fa4b2623-ab20-460a-8a9d-bf99e69d25b9) ## Directions A 'GEDI Message Code' can be configured in different Directions. This determines the main function of the 'GEDI Message Code'. The directions are; * **Down:** For importing data from a 'GEDI Message'. Usually originating from the CIP. For example, an EDI order is written to 'GEDI Message' from CIP and should be imported as a Sales order. * **Internal:** For requests to create another 'GEDI Message' with another 'GEDI Message Code'. For example, an invoice is being posted and the invoice request message is added to the 'GEDI Message Queue'. * **Up:** For exporting data to a 'GEDI Message'. Usually because the CIP should receive it. For example, when invoice data is exported to 'GEDI Message' to later be read by the CIP. * **Control:** For controlling data in Business Central. Usually checking if required fields are missing data. For example, an EDI order is imported and a control checks if there is article number match on all order lines. * **Up Auto Finished:** For a function that should be automatically marked as finished, to prevent the CIP from reading the 'GEDI Message'. For example, a PDF invoice being sent out via Business Central e-mail functionality. * **Posted:** For exporting data to a 'GEDI Message' and directly posting it up to the CIP via xml port instead of letting the CIP read the 'GEDI Message'. Usually this is only used when the CIP is not allowed to have a web service integration with Business Central. As the CIP in this case has no way of sending back information such as status updates to Business Central. For example, an EDI Invoice is sent via Basic Invoice Setup, which doesn't require a web service. Statuses for the EDI Invoice is only stored and found in the CIP portal, as they are not sent back to Business Central. # GEDI Message Setup "A 'GEDI Message Setup', is a definition of the process that is connected to each 'GEDI Profile'" ![GEDI Message Setup](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2Fu4g4TMQqBi3e0LuSuW0H%2FCC%20Message%20Setup.png?alt=media\&token=1a5d4e10-4736-4bd5-a1d6-345db0bb5c20) ## Introduction In the 'GEDI Message Setup' page view in Business Central you will find 'GEDI Message Setups'. A 'GEDI Message Setup', is a definition of how three main parameters; 'GEDI Profile', 'GEDI Message Code' and 'GEDI Mapping Document' are all tied together and build the process that is connected to each 'GEDI Profile'. For each 'GEDI Message Setup' there is a check box for "Not Create Automatically". If this is checked, the normal events defined by 'GEDI Message Selection' will be disabled for the combination of 'GEDI Message Code' and 'GEDI Profile'. This can be useful when it's better to have a 'GEDI Mapping Document' create the 'GEDI Message Code' instead of the normal event. For example, when a control is to decide wheather a 'GEDI Message' should be created or not. ![Example of what the 'GEDI Message Setup' table can look like.](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2Fidb1RoojuIhQBOZW2zuI%2Fbild.png?alt=media\&token=fccb2f99-fd15-4c05-8e4a-48562a564c24) # GEDI Message Selection "A 'GEDI Message Selections', is a definition of which events that should trigger 'GEDI Messages'" ![GEDI Message Selection](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FWyrj83yyF4znNVhGpSEb%2FCC%20Message%20Selection.png?alt=media\&token=54509e9d-af1e-48f0-9e61-9d1a43865c75) ## Introduction In the 'GEDI Message Selection' page view in Business Central you will find a overview of all 'GEDI Message Selections'. A 'GEDI Message Selection', is a definition of which events in Business Central should trigger which 'GEDI Message Codes' to be created as 'GEDI Messages'. ![Example of how the 'GEDI Message Selection' overview can look like](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FCJJRikHEyQi0pOL8UpEO%2Fbild.png?alt=media\&token=0c8635d0-d7b1-4f29-9f25-a4cd561180f7) The events are also categorized in subpages, as can be seen on the picture bellow. In general, the main 'GEDI Message Selection' overview is better to use for review, and the exact subpage is better for editing. ![Examples of different 'GEDI Message Selection' subpages](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FIO2dhMEECHZ15GD37jw7%2Fbild.png?alt=media\&token=79a58b1a-87a0-4209-b0cb-1cf550b4a776) A 'GEDI Messages' will only be created if the 'GEDI Profile' that runs the event, is allowed to use the 'GEDI Message Code' as defined in the 'GEDI Message Setup'. For example, multiple 'GEDI Message Codes' could be defined on the same event, but depending on the 'GEDI Profile' running the event, only some or all of the 'GEDI Message Codes' will actually trigger 'GEDI Messages'. ## Active and Passive Events Some events are Active and some are Passive; * **Active events:** Events that are tracked when they happen, and then creates the 'GEDI Message' with the 'GEDI Message Code'. Usually this is standard Business Central events. For example, Posting of a Invoice, Release of an Order etc. * **Passive events:** Only to define which job queue Categories should run which 'GEDI Message codes' in the 'GEDI Message Queue'. The actual 'GEDI Message' is created by another source than the event itself. For example, the CIP created a incoming sales order, a 'GEDI Mapping Document' created a status update. ## Processing Methods There are two different options to configure how the 'GEDI Message' should be processed; by a Job Queue Entry or "immediate". Most events will only work with either of the two options, and this is predefined. * **Job Queue Processing:** Configured by selecting a 'Job Queue Category Code' that should process the 'GEDI Message Code'. This is the most common method and is used for almost all export, import and other actions that can be processed in the background. For example, the event "S.Invoice" happens after a Sales Invoice has been posted. The 'GEDI Message Code' for the Sales Invoice export request will be created in the 'GEDI Message Queue'. And the actual execution of the export will be done later by the Job Queue Entry with the corresponding Category Code. * **Immediate Processing:** Configured by checking the "Manual Immediate Run" checkbox. Usually this means that the 'GEDI Message Code' defined is a control that will be processed directly. Either in the interface or in the background. This processing method is for example used for pop-up controls or for export of temporary data. For example, the event "C.S.Invoice" happens when a Sales order is requested to be posted for invoicing. This enables the control 'GEDI Message Code' to either allow or rollback the posting event. In the control, certain fields that are required for allowing the posting can be defined. If requirements are not met the posting event will be rolled back. # GEDI Mapping "A 'GEDI Mapping Document', is a definition of rules to be applied when processing" ![GEDI Mapping](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FuuK5bWFfxTtG4G1TbXFk%2FCC%20Mapping.png?alt=media\&token=4317220d-6b8e-4db3-ba90-53376b391ef6) ## Introduction In the 'GEDI Mapping List' page view in Business Central you will find 'GEDI Mapping Documents'. A 'GEDI Mapping Document', or short 'GEDI Mapping', is a definition of tables and fields in Business Central that should be exported from, imported to or be controlled. Along with rules and filters to be applied. The 'GEDI Mapping' is structured in a table and processed from top to bottom row. There are many different types of rules that can be used, and new rules are often added upon release of new Standard App versions. This allows for a very powerful and flexible framework that can be used for much more than just EDI. ## Mapping Concepts 'GEDI Mappings' can be divided into some different concepts; * **Import:** Moving data from 'GEDI Messages' into tables and fields in Business Central. * **Export:** Moving data from tables and fields in Business Central to 'GEDI Messages'. * **Control:** There are different types of controls. For example controlling if fields in Business Central contains certain values or if they are empty etc. * Can be used as a pop-up error at certain events, for example release of Order or other Posting events. * Can be used to create comments in Business Central. * Can be used as "If this then that" rules to generate new 'GEDI messages'. The result can for example be triggering an error message to be sent by e-mail or a record to be updated with a 'GEDI status'. * **Send PDF**: Generate PDF mails with the Standard Business Central functionality, using the automization logic from the Standard App. For example, when Invoice is posted, then the Invoice PDF will be automatically e-mailed to the customer as per configuration. * **Internal functions:** Running only internal functions, such as updating a status, creating a 'GEDI Message Log' or running a Code Unit. ## Classes and Properties As previously mentioned, the CIP integrates with the Standard App via an internal JSON format. In the Standard App the JSON format is structured by 'GEDI Class names' and 'GEDI property names'. * 'GEDI Class names' correspond to a Message Document type, for example 'ORDER' or 'INVOICE' etc. * 'GEDI Property names' correspond to a field or 'tag' as it's often called in EDI, for example 'OrderNumber' or 'InvoiceNumber' When creating import mappings or export mappings, one of the main purposes is to define the rules for which Business Central tables and fields shall correspond to which 'GEDI Class Name' and 'GEDI Property Name' in the internal format. # GEDI Conversion Lists "A 'GEDI Conversion Document', is a table used for converting specific values" ![GEDI Conversion Lists](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FzTpA6Ms9t7r7xXXTq6jJ%2FCC%20Conversion%20Lists.png?alt=media\&token=2d5485af-a027-44b1-b743-c26f0d2e9478) ## Introduction In the 'GEDI Conversion List' page view in Business Central you will find 'GEDI Conversion Documents'. A 'GEDI Conversion Document', or short 'GEDI Conversion', is a table were you can input values to be converted and used in 'GEDI Mappings' or in Code Units. This means that code identifiers inside Business Central can be different from the code identifiers in the EDI. ## Conversion Concepts In general you can divide 'GEDI Conversions' into some different concepts; * **Identifier:** Convert internal Business Central identifiers to or from standard EDI codes used by the 'CIP translators'. For example, maybe in Business Central a unit of measure is "BX" but the corresponding EDI standard code is "BOX". Then a 'GEDI Conversion' is used to convert the values. * **Add Info:** Can be used to add information that has no field in Business Central. For example, A customer has a fixed invoice reference they require in EDI. Then a 'GEDI Conversion' could be used to convert the customer nr into the fixed invoice reference and include in the EDI message. * **Logical:** Can be used to convert fields in Business Central to a integer. The integer can then be used in 'GEDI Mapping' rules or in the 'CIP Translator' to flag certain scenarios. For example, some order rows are articles and some are not. If we convert ARTICLES to 1, RESOURCES to 0 and G/L ACCOUNTS to 0; then we can tell the 'CIP Translator' that some rows are item related (1) and some rows are are not (0). # GEDI Message Log "A 'GEDI Message Log', contains information about when a 'GEDI Message' has been processed" ![GEDI Message Log](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FF2IoBZ1SNUFSH8vL9rjw%2FCC%20Message%20Log.png?alt=media\&token=6ef1153e-e25a-4d60-81bf-e5996bdfac2e) ## Introduction In the 'GEDI Message Log' page view in Business Central you will find an overview of all 'GEDI Message Logs'. A 'GEDI Message Log', contains information about when 'GEDI Message' has been processed. Also some other context information regarding the processing is saved in the 'GEDI Message Log'. Not all processed 'GEDI Messages' will create a 'GEDI Message Log'. How and when a 'GEDI Message Log' is created is determined by the 'GEDI Mapping' rules. Creating a 'GEDI Message Log' connected to a record will allow for the 'GEDI Status' to be updated after processing. Therefore it is recomended to create a 'GEDI Message Log' for the 'GEDI Mappings' where a 'GEDI Status' update is relevant. ## Duplicate protection One of the purposes of the 'GEDI Message Log' is to track which key references are already used by other 'GEDI Messages'. It is very common in a EDI process that updates are not allowed against the same key reference. This is prevented by setting the 'GEDI mapping' to "not allow updates", and by creating a 'GEDI Message Log' on the key reference. For example, you have received the same sales order twice from a customer by mistake. The first time the order gets imported and the customer purchase order number is stored into External Document Number field and saved as a 'GEDI Message Log'. The second time you receive an order with that same customer purchase order number, the import will be stopped automatically and an error e-mail sent out. ## **Processing protection** Another purpose of the 'GEDI Message Log' is to track if a request is executed or not. This can be useful to prevent certain events to create a second request before the first is executed. For example, a sales order is released and the event creates a request for an order confirmation to be processed. If the user want to reopen the sales order again, they have to wait for the first order confirmation to be executed, before reopening the order is allowed. This is to make sure that the sent order confirmation correspond to the sales order at the time it was released. The processing protection can be disabled in the corresponding 'GEDI Mapping Document'. # GEDI Status Ledger "A 'GEDI Status Ledger Entry' contains status information to be displayed for the end user" ![GEDI Status Ledger](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FghJ0y3LLAha0VicQGRV7%2FCC%20Status%20Ledger.png?alt=media\&token=39d89fcb-1042-4cb6-af59-692b1a86c8d0) ## Introduction In the 'GEDI Status Ledger Entries' page view in Business Central you will find a overview of all 'GEDI Status Ledger Entries'. A 'GEDI Status Ledger Entry' or short 'GEDI Status', contains information that should be displayed on a record for the end user. A 'GEDI Status' is always connected to a 'GEDI Status Code'. On a a lot of records you will find a field called 'GEDI Status'. In this field you can see the latest Status Description of 'GEDI Statuses' connected to this record. This allows the end user to get a quick overview of what the latest status for a record is. If the 'GEDI Status' field is empty, it usually means that this record did not trigger any GEDI processes. ![Example of what the 'GEDI Status Ledger Entries' table can look like](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FUwNnx6uMEIIRinbT5cqJ%2Fbild.png?alt=media\&token=5a6feee2-22bb-441d-a245-420ab0391477) ![Example of how 'GEDI Status' is viewable on a document type, in this case in the Sales Order list.](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FIDVQAivnWUpG27RSovUG%2Fbild.png?alt=media\&token=2d70a67d-ce34-480b-b03c-142dedda33c2) # GEDI Status Codes "A 'GEDI Status Code', is a definition of which status texts that can be configured" ![GEDI Status Codes](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2F0jvXJlSsUhu2PfWYavYS%2FCC%20Status%20Codes.png?alt=media\&token=ba39d507-adb2-40ba-83c4-88e05d62db48) ## Introduction In the 'GEDI Status Codes' page view in Business Central you will find 'GEDI Status Codes'. A 'GEDI Status Code', is a definition of which status texts that can be configured. The 'GEDI Status Code' is connected to a 'GEDI Message Code'. When a 'GEDI Message' is created or executed, depending on the configuration, a 'GEDI Status' will be created. The status codes description can be changed or translated as needed, without any impact on the configuration. ## Status concepts 'GEDI Status Codes' can be divided into some different concepts. * **Direct:** Is created when a 'GEDI Message' is created. For example, an Invoice is posted and directly gets the status "**EDI Requested**". This is before the 'GEDI Message' request is executed. * **Processed:** Is created when the 'GEDI Message' is executed. This is connected to a 'GEDI Message Log' that is created during the execution. For example, the above invoice 'GEDI Message' request is now executed and is waiting for the CIP to read the information. The 'GEDI Status' is now set to "**EDI Sending**". * **CIP:** Is created when the CIP writes a 'GEDI Message' when a new status in the CIP has been reached. This is connected to a 'GEDI Message Log' that is created during the execution. For example, the above invoice is now translated by the CIP and sent to the receiver as EDI. Then CIP writes back a "sent" 'GEDI Message'. When this "sent" 'GEDI Message' is executed, the invoice 'GEDI Status' will be "**EDI Sent**" * **Control:** Is created when a Control mapping is executed and the outcome of the control will be either True or False. Then two different Statuses can be connected to this. For Example, a sales order is imported via EDI and now a control is checking if all article numbers from the customer can be matched against the item list in Business Central. If the outcome is that all article numbers match, then the 'GEDI Status' "**OK Control**" is created. If the outcome is that not all article numbers match, then the 'GEDI Status' "**Error in Control**" is created. ## Status Color Schemes All statuses can be configured to be visualized based on a color scheme. Some transactions has a GEDI list page view, for example 'GEDI Posted Sales Invoices'. In these list pages the 'GEDI Status' field will be presented by the color scheme defined. The Status color Schemes are; * **Standard, in black.** Used when there is only one outcome. For example, "EDI Requested" when the invoice was posted. * **Ambiguous****, in yellow.** Used when the outcome is not yet known. For example, "EDI Sending" when the EDI invoice is executed, but the CIP has not yet written down the next status. * **Favorable****, in green.** Used when the outcome is positive. For example, "EDI Sent" when the invoice was sent to receiver by the CIP. * **Unfavorable****, in red.** Used when the outcome is negative. For example, "Error in Control" when the order control found article numbers that didn't match. # GEDI Message Lines "'GEDI Message Lines', holds the information that is contained within a 'GEDI Message'" ![GEDI Message Lines](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FpBHh6tgdyCg1utYbwUUm%2FCC%20Message%20Lines.png?alt=media\&token=fbded767-3d75-43ad-9309-64d9d184c6f6) ## Introduction In the 'GEDI Message Line' page view in Business Central you will find 'GEDI Message Lines'. 'GEDI Message Lines', holds the information that is contained within a 'GEDI Message'. The information is structured by 'GEDI Class name' and 'GEDI Property name'. * 'GEDI Class names' correspond to a Message Document type, for example 'ORDER' or 'INVOICE' etc. * 'GEDI Property names' correspond to a field or 'tag' as it's often called in EDI, for example 'OrderNumber' or 'InvoiceNumber' 'GEDI Mappings' can import or export information to 'GEDI Message Lines'. The CIP reads or writes information to 'GEDI Message Lines'. ## Value types Each 'GEDI Message Line' and each corresponding 'GEDI Property name' has a specific value type. This makes sure that information is always imported and exported correctly. Each value type has it's own column in the 'GEDI Message Line' table. The value types are; * Text value - "Customer Name" * Code value - "PIECE" * Integer value - "100" * Decimal value - "100,00" * Date value - "2021-10-29" * Time value - "10:15:00" * DateTime value - "2021-10-29 10:15" * Boolean value - Checkbox for "TRUE" or "FALSE" * Big integer value - "12147483647" The value type defined in the 'GEDI Mapping' shall correspond to the value type of the 'GEDI Property name', or the data won't be correctly transferred. ## Levels 'GEDI Message Lines', 'GEDI Class names' and 'GEDI Property name' all have a corresponding level. Levels allow for different 'GEDI Class names' to together build up one 'Message Document Type'. The level can be found in a field in the 'GEDI Message Line' For example, 'Message Document Type' 'Order' consists of two levels and 'GEDI Class names': * Level 1: 'ORDER' 'GEDI Class name', corresponds to the order header. * Level 2: 'ORDERLINE' 'GEDI Class name', corresponds to the order lines. Some 'Message Document Types' and 'GEDI Class names' may have repeatable levels. To structure this information there is a field 'Level Line No' on each 'GEDI Message Line'. For example, many 'ORDERLINE' 'GEDI Class names' can be contained in the same Order. * First 'ORDERLINE' section has 'Level'=2, and 'Level Line No'=1 * Second 'ORDERLINE' section also has 'Level'=2, but 'Level Line No'=2 * etc for each additional line. Some 'Message Document Types' are more complex than others. For example, the Despatch Advice has three levels and 'GEDI Class names'. The Despatch Advice header can hold multiple containers and each container can hold multiple order lines. * Level 1: DESPATCHADVICE - Despatch Advice header information * Level 2: DESPATCHADVICELOGISTICUNIT - Despatch Advice container information * Level 3: DESPATCHADVICELOGISTICUNITLINE - Despatch Advice article line information # GEDI Class Setup "A 'GEDI Class Setup', is a definition of which 'GEDI Message Code' should be used by the CIP." ![GEDI Class Setup](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2Fwds2tiMMtffqrLd20BzK%2FCC%20Class%20Setup.png?alt=media\&token=f7b05036-a9e7-4286-8f50-91e509980396) ## Introduction In the 'GEDI Class Setup' page view in Business Central you will find 'GEDI Class Setups'. A 'GEDI Class Setup', is a definition of which 'GEDI Message Code' should be used by the CIP when writing 'GEDI Messages' to the 'GEDI Message Queue'. This is defined per 'GEDI Class name' used for the header of the 'Message Document Type'. For example, the CIP wants to write a new Order 'Message Document Type' into the 'GEDI Message Queue'. ORDER is the header 'GEDI Class name' for Order 'Message Document Type'. ORDER can then be defined in the 'GEDI Class Setup' with 'GEDI Message Code' "SO-01-IM". The CIP can now create a 'GEDI Message' with 'GEDI Message Code' "SO-01-IM". It is possible for the CIP translator to have rules for fallback or override 'GEDI Message Code' as well. In 'Reference Property names' field it is possible to determine which 'GEDI Property name' should be used as the 'Message ID' for the 'GEDI Message' that the CIP creates. ![Example of what the 'GEDI Class Setup' table can look like](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FH0YsW4KsjMzyxKDlVqnu%2Fbild.png?alt=media\&token=ffb9de57-ad28-46de-8060-deff464fc3a0) # Jobb Queue Entries "'GEDI Messages' is usually configured to be automatically processed by 'Job Queue Entries'" ![Job Queue Entries](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4Q6J1fzsyYoa0sjFct%2Fuploads%2FWFbezVwx2O2BOlytD75T%2FCC%20Job%20Queue%20Entries.png?alt=media\&token=37c5f76a-2cfe-4df6-a91c-c9575d89fcce) ## Introduction 'GEDI Messages' is usually configured to be automatically processed by 'Job Queue Entries'. 'Job Queue Entries' are configured to call on specific Code Units and 'Job Queue Category Codes'. 'Job Queue Category Codes' are then configured against an event and 'GEDI Message Code' in the 'GEDI Message Selection'. There are some standard 'Job Queue Entries' that many 'GEDI Setups' relies on, for example the 'Job Queue Category Code' 'GEDIQUEUE'. Additional 'Job Queue Categories' can be configured if certain 'GEDI Messages' should be processed on other time interval than 'GEDIQUEUE'. The CIP has the possiblity to track if the 'Job Queue Entries' are still running as expected. This functionality is called a 'GEDI Heartbeat'. If the 'Job Queue Entry' for some reason should stop running, the CIP can send out notifications about 'GEDI Heartbeat' failure. ![Example of how a 'GEDIQUEUE' 'Job Queue Entry' can be configured. Processing every 5min during selected days and times.](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FMRSPK5tMk0qiwNQQJKlL%2Fbild.png?alt=media\&token=5c2b882c-9d89-4580-8375-61fbec941a1c) There can also be other GEDI related Code Units that 'Job Queue Entries' could call upon. For example, when configuring an automatic master data sync, a 'Job Queue Entry' defines how often the sync should run. ## GEDIDELETE Another 'Job Queue Entry' that should be configured in most Standard App installations is the 'Job Queue Category Code' 'GEDIDELETE'. 'GEDIDELETE' is a clean up job that deletes old 'GEDI Messages' depending on a setting in the 'GEDI Message Code'. This job is most often run once a day making sure that 'GEDI Messages' doesn't store too much information over time. ![Example of how a 'GEDIDELETE' 'Job Queue Entry' can be configured.](https://4116199904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCnajZpb6jyP8d1VA5elK%2Fuploads%2FJbv2lSssDctdnSd1AcW2%2Fbild.png?alt=media\&token=0df3d413-ba43-4b2b-ad9b-cf7e8c7999f3) # Core Concepts Click the link to go back to Core Concepts Collection {% content-ref url="/spaces/Fe4Q6J1fzsyYoa0sjFct" %} [Core Concepts](https://docs.goldenedi.com/core-concepts/) {% endcontent-ref %} # Implementation Academy Click the link to go back to Implementation Academy Welcome Page {% content-ref url="/spaces/5j3ssU7KCYI19mOdXAqF" %} [Implementation Academy](https://docs.goldenedi.com/) {% endcontent-ref %} # Courses Collection Courses for Golden EDI for Microsoft Dynamics 365 Business Central {% content-ref url="/spaces/FEfalHvEWA6QmvEniWuJ" %} [Beginner Courses](https://docs.goldenedi.com/beginner-courses/) {% endcontent-ref %} {% content-ref url="/spaces/CcSDbJvyHppjDQkwzuGV" %} [Broken mention](broken://spaces/CcSDbJvyHppjDQkwzuGV) {% endcontent-ref %} {% content-ref url="/spaces/KGejE2y9nfVngOCFW7LC" %} [Broken mention](broken://spaces/KGejE2y9nfVngOCFW7LC) {% endcontent-ref %} # Intro Beginner Courses for Golden EDI Standard App for Microsoft Dynamics 365 Business Central ## Welcome to Beginner Courses for Golden EDI Standard App In Beginner courses in Golden EDI Implementation Academy we will take you through the installation and initialization of the Golden EDI Standard App. We will also teach you how to implement prepacked 'GEDI Setups'. Except from the above we will talk about 'GEDI Profiles', 'GEDI Conversion tables' and standard configurations in the 'GEDI Message Codes' and 'GEDI Status Codes'. You will also learn how to manage the 'GEDI Message Queue' and Job Queue Entries related to Golden EDI Standard App. With the support of the texts, guides and videos you will get well prepared to implement Golden EDI on your self. {% hint style="info" %} Please note that the information in the Beginner Courses is not relevant for our FREEMIUM version. {% endhint %} # Installing the Golden EDI Standard App Installing the Golden EDI Standard App from Microsoft AppSource ## Introduction Installing the Golden EDI App means that you prepare Business Central to be able to use Golden EDI app for EDI flows. No actual functionality is automatically enabled upon installation, but the app will add a number of GEDI menu items and fields into Business Central. ![Example of the Golden EDI Menu in Business Central top menu. ](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FMrTntbQlvRDIyAxupKTq%2Fimage.png?alt=media\&token=871c2686-909a-488a-9564-476d514b1db3) ![Example of GEDI-fields in Customer card](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FiRUqK7Cc9EqG9bKwjmlR%2Fimage.png?alt=media\&token=a8b0ac27-99f7-4156-b239-d8ec0161a431) ![Example of GEDI-fields in Sales Invoice Document](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FfOcv9hpr3B8WDC6vazvD%2Fimage.png?alt=media\&token=a09af501-3d78-4816-be09-57351506035b) To be able to start sending or receiving EDI-messages the Golden EDI app also needs to be Initialized and configured. Depending on what EDI-flow the app shall be used for, the configuration is done either almost fully automated or with less or more manual additions. In the Beginner Courses we will focus on prepacked and "ready to use" setups done with just a few clicks. ## Prerequisites Before installing the Golden EDI Standard App, make sure the following prerequisites are full filled: * License agreement with Golden EDI signed. Each EDI-flow requires some kind of license agreement, please check with Golden EDI. * License type for your user in Business Central is a Full User. * Your permissions are set to 'SUPER' or equal. * You have permission to install Apps to the Business Central environment. * Set your Role Center to 'Business Manager' or 'Sales order processor', to get the correct menu setup for easy access the initialization of Golden EDI. ## Install Golden EDI from AppSource ### Instructions * Go to [Golden EDI](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9) app on the Microsoft AppSource. * Click 'FREE TRIAL' under the logo to install the app: ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lvlorJ3aUNYLHjLoA%2Fbild.png?alt=media\&token=2e13bf30-c13b-493a-b27e-3a02af7d2473) * You may be prompted to login to the Microsoft Office 365 account, do so if that option comes up. * Fill out the contact information and accept terms, then click on Continue. * Choose the environment where the app should be installed. ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lwziPqjPqJ3DwoixB%2Fbild.png?alt=media\&token=bf0b61b8-d5c4-416f-813f-91390c074213) * Now the app will be automatically installed in the background. * In Business Central, 'Extension Management' you can see the status. After a few minutes the Golden EDI app should say "Installed". ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lxxxAfXZcRIZSXnu7%2Fbild.png?alt=media\&token=e2fd6257-e7a1-41e5-ba2d-4287fd5c4358) ## Next step Next step is to learn how to initialize the Golden EDI Standard App. # Initialize the Golden EDI Standard App Initialize the app via a assisted setup ## Introduction Initialization of the Golden EDI Standard App means that the minimum settings to be able to run Golden EDI and proceed with setups are made. 'GEDI Classes', GEDI-specific Jobb queue Categories and 'GEDI Setup Catalogues' will be imported to Business Central. ![Some standard 'GEDI Class Setup' rows are created](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FtPCoQlImnXnbOfhySxKa%2Fimage.png?alt=media\&token=73d8cc3a-d7c4-48ab-8da5-2a7954ef84c4) !['GEDI Setup Catalog' list is downloaded](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FIISYbQ0iPCR1TVfa8UTc%2Fimage.png?alt=media\&token=c582b612-92fd-4a9a-854e-8e84c04c781c) ![GEDI-specific 'Job Queue Categories' are created.](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FUf8fmeZlHy3V0eYiEUBA%2Fimage.png?alt=media\&token=05698be5-f9ce-4c10-b58d-a56e76b388e7) ## Initialize the Golden EDI Standard App ### Instructions * In Business Central, search and go to the page 'Assisted Setup'. * In 'Assisted Setup', click on 'Golden EDI - Initialize'. ![Search on "Golden EDI" to find the Golden EDI - Initialize easier](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FHR5Jqa9bxuJ4ZIz0sKDo%2Fimage.png?alt=media\&token=3327287f-b48c-4374-bb65-f5f067af6fc9) * Accept the Terms of Use and Privacy Policy by clicking the checkbox and then 'Next'. You can find both the privacy policy and the terms of use on the [AppSource](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9). ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FM71mC1nqKMKB0eAYZ1bw%2Fimage.png?alt=media\&token=e7d18d33-513e-40df-af06-eb66728792cb) * At the next page click on 'Next' to download and import base data necessary for Golden EDI. The download will not take more than a few seconds to complete. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FlQGtpbT0kS5mB3QhEkbQ%2Fimage.png?alt=media\&token=b98d1af3-3780-43b7-abad-b5ac5a57b045) * Complete the assisted setup by clicking 'Finish'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fk6BrLlEjocUVd4qrjhOl%2Fimage.png?alt=media\&token=76685f74-c069-4e15-8aa3-f1006f04cce1) ## Next step Next step is to configure 'GEDI profiles' with proper information. # GEDI Profiles Update the 'GEDI Profile' with connection settings ## Introduction A 'GEDI Profile' is the key to which processes you want to activate in the Standard App, and what exact GEDI configurations will be used. the 'GEDI Profile' is also what connect Business Central with the Golden EDI Cloud Integration Platform (CIP). ## Extras {% hint style="info" %} More information on this subject can be found in our ['Core Concepts](/standard-app-core-concepts/concepts/gedi-profiles)'/'GEDI Profiles'. {% endhint %} ## Edit GEDI Profiles Settings ### Instructions In the following step by step guide we will update the profile named 'EDI' that originates from the import of 'Order-To-Cash' 'GEDI-setup' that was illustrated in the previous lesson. * In Business Central search and go to 'GEDI Profiles' page view. In 'GEDI Profiles' you are presented with the profiles that are currently setup in Business Central. Depending on what setups you have imported to the system the profiles will vary. There are a lot of columns in this page view but not all are relevant for each 'GEDI setup'. ![Example of GEDI Profiles originating from different 'GEDI setps'](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FpZZ6387yBCj0kVDvl948%2Fimage.png?alt=media\&token=b9dc8937-fa92-4d78-9b16-04bb128cc0fa) * Add the Connection ID that you have received from Golden EDI into column 'GEDI Connection ID'. Most often the Connection ID consists of an abbreviation of the Business Central company name and the name of the receiving party. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FAtZc2JHsE3kaEsWUVF2t%2Fimage.png?alt=media\&token=dc05a8ce-5eba-438b-a198-a5f1e05523bb) * Add the connection API Key that you have received from Golden EDI. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F5hbGii8YgrYXhy5MymON%2Fimage.png?alt=media\&token=a0d0c7a4-d241-4cee-bf7b-1427c37ae5ec) {% hint style="info" %} [Contact the Golden EDI team](http://goldenedi.com/contact) to receive API Key and other connection settings needed.\ Also you need to provide Golden EDI with Webservice details. {% endhint %} * Add E-mail addresses in the columns 'E-mail to System Administrator' and 'Email to GEDI Administrator'. These recipients will be notified via e-mail if there are any errors related to Golden EDI. For example; errors related to the Job Queue will be notified to the 'GEDI Administrator'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FQbag7owW5Gxl7Ju36FVL%2Fimage.png?alt=media\&token=48149cc3-d966-4ec1-9210-9fff10759f71) Now the profile itself is complete and ready for communicating with the CIP. ## Next Step Next step is to learn how to Import Prepacked Setups. # Import Prepacked Setup Import a complete GEDI configuration package ## Introduction A 'GEDI Setup' is an XML file containing a complete GEDI configuration package of the Standard App. Using the 'GEDI setups' is a powerful and efficient way to import GEDI configurations on company level in Business Central. ## Prerequisites Before importing any prepacked setups, make sure the following prerequisites are fullfilled: * License agreement with Golden EDI signed. Each EDI-flow requires some kind of license agreement, please check with Golden EDI. * Golden EDI Standard App is installed. See [Installing the Golden EDI standard App](/beginner-courses/lessons/installing-the-golden-edi-standard-app) for instructions * Golden EDI Standard App ha been initialized. See[ Initialize the Golden EDI Standard App](/beginner-courses/lessons/initialize-the-golden-edi-standard-app) for instructions. * Golden EDI Profile updated with proper connection information. ## Extras {% hint style="info" %} More information on this subject can be found in ['Core Concepts'/'GEDI Setup Catalogs'](/standard-app-core-concepts/concepts/gedi-setup-catalog) {% endhint %} ## Import Prepacked Setup Please see our Guides for a list of documented 'GEDI Setups' {% content-ref url="/spaces/zhgbu1mdtStXCa9HahV2" %} [Guides](https://docs.goldenedi.com/guides/) {% endcontent-ref %} In the 'GEDI Setup Catalog' page in Business Central you can also find a list of all published 'GEDI Setups' available for downloading. ### Instructions * In Business Central, search and go to the page 'GEDI Setup Catalog'. In the list you are presented with the Name, Version and a short Description of the setups. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FaXkXsL2doyPv4VvZThdx%2Fimage.png?alt=media\&token=8098286e-ca59-4e2b-9e83-a294b7aa83c5) * Choose 'New' and 'Synchronize List'. This is to make sure you have the latest versions of prepacked setups available. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FVCak3N0ZZDjdbvzf7vWL%2Fimage.png?alt=media\&token=11639318-f65a-4da3-9aa7-596a67f9f3b5) * Select the setup you like to import and then choose 'Process' and 'Synchronize setup'. If there are more than one version available for the setup always choose the latest one. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Ff4LrZXNsJ1Ec8HFbV5I0%2Fimage.png?alt=media\&token=c75af8e7-af07-4b15-95b5-e6d19ae8e552) Once the Synchronization is done the checkbox in column 'Importable' will be checked. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FryJ8aptEb88IGUDI46Z5%2Fimage.png?alt=media\&token=8ea39f38-6e80-463f-9cf0-cf247f4caacc) * Now choose 'Process' and 'Import Setup' to import the GEDI configurations related to the selected setup. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FsdUQVWYz1S1NVMEtXu3j%2Fimage.png?alt=media\&token=a5a99e4e-da50-494d-8823-e8bc398accf8) * A popup will ask you to confirm that you like to import the Setup. Press 'OK'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FqZQgMXo3QY7bQCSsdGsw%2Fimage.png?alt=media\&token=b1ec9fa1-eef6-421a-a0a9-732d156eff1c) {% hint style="danger" %} When you import a setup it is possible to replace and overwrite current setups by enabling Delete Existing Setups. Make sure this option is not enabled if not intended. {% endhint %} * Another popup will ask you to confirm again. Press 'Yes'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F2hiC5ElNCa05iCoSyPuf%2Fimage.png?alt=media\&token=b9d27101-8c5a-41fc-bb2f-47993207fdbc) * After a few seconds the setup is completed and you will return to the 'GEDI Setup Catalog' page. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FEExV9FOr8ee3Fd5mw1ns%2Fimage.png?alt=media\&token=982823d1-2941-41f1-af25-e83d97f34452) {% hint style="info" %} The prepacked 'GEDI Setups' can be imported on top of each other without conflict with already downloaded setups. {% endhint %} ## Next Step Next step is to learn how to do a backup of the GEDI configuration. # Backup Current Setup Backup the complete GEDI configuration ## Introduction Once you have finalized a configuration or added a new setup to Business Central it is well advised to save a backup of the complete confiugration. That way it will be easy to restore your GEDI Coinfiguration if needed. Back up is easely done from the 'GEDI Setup Catalog' page. ## Extras {% hint style="info" %} More information on this subject can be found in our ['Core Concepts'/'GEDI Setup Catalogs'.](/standard-app-core-concepts/concepts/gedi-setup-catalog) {% endhint %} ## Backup Current GEDI Setup ### Instructions * In 'GEDI Setup Catalog' page click 'New' and 'Save Current Setup' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FV52zyJek6I2D0ML42KpR%2Fimage.png?alt=media\&token=3c757c48-64fd-4984-a198-16bc1a946ae7) * Add Name, Version and Description for your backup. Best practice is to add the date of the back up in the Version field. Press 'OK'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FmwitVh2NyAfAWZuvq9bj%2Fimage.png?alt=media\&token=f4ffbd4d-d83f-4339-a7c9-a1b59a6559a9) Now a backup of your GEDI configurations has been saved and is possible to import if it should be needed to restore configurations at some point.
![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FhxcUYW6tpdFFnVbxZH99%2Fimage.png?alt=media\&token=9b3cdb0f-fa46-48c0-8f29-3445875f1e92) ## Next Step The next step is to update the Customer/Vendor Card with the correct 'GEDI Profile'. # Customer/Vendor GEDI Profile ## Customer/Vendor GEDI Profile All customers or vendors that you are going to have an EDI connection to needs to have a Golden EDI profile set in the customer/vendor card. * In Business Central go to 'Customer/Vendor Card' for the relevant entity. * In section 'Invoicing' click the drop down in the field 'GEDI profile' and select the relevant profile. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FB5d8nuqFipl3arKBxnmj%2Fimage.png?alt=media\&token=e3e3e68a-ef55-437c-9a77-b073cd24dd5c) ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FjiqJTI9lLvlZ5cK3CMXp%2Fimage.png?alt=media\&token=60b22976-4110-409f-966c-6e0ab0734e9b) Choosing the 'GEDI profile' will trigger the EDI functionality. The 'GEDI Profile' will be inherited to each new document for this specific customer/vendor. {% hint style="warning" %} Any already existing documents for the customer/vendor will not be updated with the chosen 'GEDI profile'. If EDI functionality shall be used for already existing documents, then the 'GEDI Profile' needs to be added to each document. {% endhint %} ## Next Step The next step is to update Documents with the 'GEDI Profile'. # Document GEDI Profile ## Document GEDI Profile Each document created against a customer/vendor having a 'GEDI Profile' will inherit that profile. The document 'GEDI profile' is usually found under the section 'Invoice Details'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F2YSykUelO7gLO2fgBUZY%2Fimage.png?alt=media\&token=265b073e-f44f-45b4-a423-e44b2820fd7e) * To add a 'GEDI profile', go to the specific document. * In section 'Invoice Details' click the drop down in the field 'GEDI Profile' and select the relevant profile. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F1VW4WyC3BHz2h5droPmW%2Fimage.png?alt=media\&token=d1ec49ee-3a7d-40ea-857c-5c8312d16617) ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FPA5yMCnbM1T7kSM42ohx%2Fimage.png?alt=media\&token=f0ee9429-9153-496d-b005-44817cbc7028) {% hint style="info" %} If you want to exclude a document from EDI functionality the 'GEDI Profile' needs to be removed from the document before next event such as releasing or posting. {% endhint %} * To remove the 'GEDI Profile', go to the specific document. * In section 'Invoice Details' highlight the text in the field 'Gedi Profile' and press delete on your keyboard. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FLECyOLrvBN3bR8MjTe1B%2Fimage.png?alt=media\&token=7555452e-7e0b-4506-8b47-3a3924536699) ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FvsWIwKf827WdEAAgvnVP%2Fimage.png?alt=media\&token=00b09edc-bb27-4088-94e0-6d9e0e125659) ## Next Step Next step is to learn about 'GEDI Conversion Lists'. # GEDI Conversion Lists Convert Business Central internal code identifiers to values needed by Golden EDI ## Introduction A 'GEDI Conversion Document', or short 'GEDI Conversion', is a table were you can input values to be converted between what's needed by Golden EDI and what's needed by Business Central. This means that code identifiers inside Business Central can be different from the code identifiers in the EDI. Whether a 'GEDI Conversion' will be needed or not is decided by the setup. Some setups don't require any 'GEDI Conversions' while other require more than one. We will have a look on what the conversion documents may look like and how to edit them. In the 'GEDI Conversion List' page view you are presented with the existing 'GEDI Conversion documents' with Name, Description, Creation date, Edited date and a setting showing if it is Enabled or not. Two of the most common 'GEDI conversions' are CURRENCY and UNIT-STD ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FqykodgeVjxC8dmHD47gr%2Fimage.png?alt=media\&token=834400b0-e214-4f77-afa2-2c08d693af90) In the 'GEDI Conversion List' page view you will find the document header with the information listed in the 'GEDI Conversion List' page view, and with details for each converted value. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FS5Pw2f8OlYPRetVAROIO%2Fimage.png?alt=media\&token=4c80d870-6bcf-4178-86b6-3e926653b34e) ## Extras {% hint style="info" %} More facts about 'GEDI Conversion Lists' can be found in our ['Core Concepts/'GEDI Conversion Lists'](/standard-app-core-concepts/concepts/gedi-conversion-lists). {% endhint %} ## View and Edit GEDI Conversion Documents ### Instructions * In Business Central search and go to 'Gedi Conversion List'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FaeDco3p1771PASoZl79h%2Fimage.png?alt=media\&token=c8f61be7-91a9-4b78-b763-0fca796f5a52) * Click on the 'GEDI Conversion' that you like to open and 'GEDI conversion Document' page view will show you the document details. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FhFlKNvyuPDuHgUimTRno%2Fimage.png?alt=media\&token=88917cb8-1706-47aa-ab74-13933f7e50da) #### Columns 'Description': Present you with the description from the Value in column 'Code Value 1' 'Conversion Type': Let you know that the 'GEDI conversion document' are going to convert from one code value to another. 'Code Type 1': Tells you what table in Business Central holds the value to convert. This field is optional. 'Code Value 1': Shows what code value from the Business Central table that shall be converted. 'Code Value 2': Is the Value that 'Code Value 1' will be converted into. {% hint style="info" %} The direction of the convertion to/from Code 1 is decided by the 'GEDI Mapping' using the specific 'Gedi Conversion Document' {% endhint %} #### Add new Record * Open the relevant 'GEDI Conversion Document'. * Click to add new Line. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FuYrcXySRNbkrQElqw492%2Fimage.png?alt=media\&token=5f21f505-3074-4501-b899-ff21b0d65bcb) * Move to 'Code Type 1' and click the drop down to select the correct value from the list. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FU6Aa4Y0KONrlSVVnOSH5%2Fimage.png?alt=media\&token=0aa20581-663a-4d72-ba37-3535ccd8dacb) * Move to 'Code Value 1' and click the drop down to select the record you like to add. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fhul3OXo4S09lwq8ayTXq%2Fimage.png?alt=media\&token=bc1aceb8-2f32-4294-9629-2af5485d598d) * Move to 'Code Value 2' and enter the code value you like to convert the selected record into. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FECOGOa5GAsH9YjdLAiCx%2Fimage.png?alt=media\&token=ae6b5b79-030d-45b7-a9c1-91d6d3806953) ### EDI Standard Codes #### Currencies Golden EDI uses the ISO standard codes for Currencies. If the Business Central company use other codes than ISO standard make sure to update the Currency Conversion Document. {% hint style="warning" %} The Currency conversion document also needs to have to lines with description Local Currency according to this example. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FvHD3fy88XkLfL2wBCTnL%2Fimage.png?alt=media\&token=56405acb-3129-400f-a79c-dbe72b59094a) {% endhint %} #### Units Please make sure that the UNIT-STD Conversion Document converts units into the codes specified in our list of [EDI standard codes for units of measure.](/standards/cip/units-of-measures) {% hint style="warning" %} From EDI point of view, items with units like "10-pack" should rather be items with unit "Piece" and a description saying 10-pack. {% endhint %} {% hint style="info" %} For Currencies and Units of Measures there is a function to copy all the current table values into the Conversion Document. In the Conversion Document press Copy and select the table you like to copy values from. The values will be inserted with Code Type and Code Value 1. \ \ ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FRN80rOWRUybU0Qfp17e8%2Fimage.png?alt=media\&token=668ffac3-7407-4515-a4a4-2211e5d6d8f4)\ \ ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FKoesZITiwTolivUaBcvD%2Fimage.png?alt=media\&token=ccc5faab-514f-420d-9184-b7110f3ae635) {% endhint %} {% hint style="info" %} In the 'GEDI Conversion' it is possible to convert Business Central Optionvalues into Code Values. {% endhint %} {% hint style="info" %} In the 'GEDI Conversion' It is possible to combine two values from Code 2 to convert into correct Code Value 1. {% endhint %} ## Next Step Next step is to learn how to configure Job Queue Entries for Golden EDI. # Job Queue Entries Configure 'Job Queue Entries' to automatically process 'GEDI Messages' ## Introduction In 'Job Queue Entries' scheduled jobs to automatically process 'GEDI Messages' are configured. The 'Job Queue Entries' page view present a list with current 'Job Queue Entries' with information about what object to run, how often, the current status etc. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F462NJhnb7q4y1w5SDTQe%2Fimage.png?alt=media\&token=c064fc88-9ca7-443a-9a4f-f93996a8aba7) ## Extras {% hint style="info" %} More information on this subject can be found in our [Core Concepts/'Job Queue Entries'.](/standard-app-core-concepts/concepts/jobb-queue-entries) {% endhint %} ## Configure Job Queue Entries ### Instructions There are three different main 'Job Queue Entries' that usually needs to be configured. \ Each queue settings are depending on the EDI-flows specific needs and the settings below are just examples. 1. **GEDIQUEUE**: will be set on a 5min schedule, each workday between 07:00 & 20:00, and will process all new messages to the Cloud Service 2. **GEDIDHEART**: will be set on a 5min schedule, each workday between 20:01 & 20:30, and will check that the communication with Cloud Integration Platform is up and running. 3. **GEDIDELETE**: will be set on a once a day schedule, at 04:00, and will clean up old GEDI data no longer needed. {% hint style="danger" %} If you have multiple Golden EDI solutions combined in your Business Central Company, and you already have Job Queue Entries configured, you don't need to create new identical ones!\ e.g. if 'GEDIDELETE' already exist, don't create another one. {% endhint %} * In Business Central, search and go to the page 'Job Queue Entries' #### GEDIQUEUE - Job Queue Entry Card * Click new to create a new 'Job Queue Entry Card'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fz6ao9mt9lBsDT1MazGek%2Fimage.png?alt=media\&token=ae5b6af7-7948-43eb-b7ef-85ef304d7cf0) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FsBhz5xJIsxNDe0fdiToL%2Fimage.png?alt=media\&token=54720d75-051d-4abf-ad99-30cfef9e8341) * Fill in the 'Job Queue Entry Card' for 'GEDIQUEUE' as per screenshot or list below. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2ldF5Ogu5xZEyXimzB%2Fuploads%2FDST0lNcNLwwM8LBBWdq1%2Ffile.jpeg?alt=media) #### General Section: | Field | Value | | ----------------------- | ------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019001** | | Job Queue Category Code | **GEDIQUEUE** | #### Recurrence Section: | Field | Value | | --------------------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 0700 | | Ending Time | 2000 | | No. Of Minutes between Runs | 5 | * The 'GEDIQUEUE' 'Job Queue Entry' is now setup to processing the EDI messages automatically every 5min, each workday between 07:00 and 20:00 * Close the Pop-up and **don't set the job queue to ready yet.** #### GEDIHEART - Job Queue Entry Card * Click new to create a new 'Job Queue Entry Card' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FRyHSh82MJhzWNy4xbffq%2Fimage.png?alt=media\&token=cd10b5c7-38bd-487f-8cb9-2cb35bce8bb0) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FsBhz5xJIsxNDe0fdiToL%2Fimage.png?alt=media\&token=54720d75-051d-4abf-ad99-30cfef9e8341) * Fill in the 'Job Queue Entry Card' for 'GEDIHEART' as per screenshot or list below. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FDk16iM9V9QAlHHuTW5Gv%2Fimage.png?alt=media\&token=1d2b2902-d651-4c0c-9648-eb987c27e5eb) #### General Section: | Field | Value | | ----------------------- | ------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019001** | | Job Queue Category Code | **GEDIHEART** | #### Recurrence Section: | Field | Value | | --------------------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 2001 | | Ending Time | 2030 | | No. Of Minutes between Runs | 5 | * The 'GEDIHEART' 'Job Queue Entry' is now setup to processing the EDI messages automatically every 5min, each workday between 20:01 and 20:30 * Close the Pop-up and **don't set the job queue to ready yet.** #### GEDIDELETE - Job Queue Entry Card * Click new to create a new 'Job Queue Entry Card' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FUXagSAzphfOos0aTFpRy%2Fimage.png?alt=media\&token=642f36f3-1016-49e3-9ce7-dde1163d72df) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FJL1luwKRCxfiYZyels46%2Fimage.png?alt=media\&token=60956fd9-4892-4b80-b179-fdac35bbe4b9) * Fill in the 'Job Queue Entry Card' for 'GEDIDELETE' as Screenshot or list below. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2ldF5Ogu5xZEyXimzB%2Fuploads%2FjyzTray2N1rVvKuAHtNP%2Ffile.jpeg?alt=media) #### General Section: | Field | Value | | ----------------------- | -------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019006** | | Job Queue Category Code | **GEDIDELETE** | #### Recurrence Section: | Field | Value | | ----------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 0400 | * The 'GEDIDELETE' 'Job Queue Entry' is now now setup to clean up old GEDI data no longer used once a day at 04:00. * Close the Pop-up and **don't set the job queue to ready yet.** ## Start the Job Queue Entries Once the setup is ready for Go Live the three GEDI-related Job Queue Entries needs to be set to Ready. ### Instructions * In Business Central search and go to 'Job Queue Entries' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FylEpGmbCndR7Hte7fw67%2Fimage.png?alt=media\&token=c123e773-e3c2-4b39-8440-07c3ff037d4e) * Select the 'Job Queue Entrie' that you like to start and click Set Status to Ready
![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FdwMzegUOhC6t0aNt72CO%2Fimage.png?alt=media\&token=f31ac619-e55d-45e9-b2f3-e339b7282d87) The status will change to Ready. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FAFN8BfFAJJzS7nXOGEgG%2Fimage.png?alt=media\&token=a7e89512-7eca-4e72-a903-a595b4b0cae5) {% hint style="danger" %} Please note that the user starting the 'Job Queue Entries' needs to have permission set to proper rights to be able to run the job. This is due to that the user starting the job queue is actually performing all the actions inside Business Central. E.g. sending e-mail, creating order etc. {% endhint %} {% hint style="danger" %} After setting the status to Ready check that Earliest Start Date/Time is in the future else it will run as expected. {% endhint %} ## Next Step Next Step is to learn how to manage the 'GEDI Message Queue'. # GEDI Message Queue Manage EDI messages within the GEDI Message Queue ## Introduction A 'GEDI Message', is something that will be, or have been processed within the Standard App. For example an Invoice that has been sent out or an order that has been imported, etc. The 'GEDI Message Queue' page view present a list of all messages that have been or shall be sent. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FG3IH6IJfQ2Ir8ZHAx64H%2Fimage.png?alt=media\&token=da7a5cc9-1eb8-4c83-aeb2-c3d0927c1196) 'Entry number' is a sequence number generated by Business Central. 'Message Code' is the specific 'GEDI Message Code' for the function that shall be executed with the message. For example SI-03-EX = Export invoice, SO-01-IM = Import order. Click on the message code to see the description. 'GEDI Profile' is the specific profile that has generated the message. ‘Message ID’ is the ID that the specific message originates from. For example the Invoice number of an Exported Invoice. Or the Business Central internal order number for an imported order. ‘GEDI Message ID’ is the unique CIP Work Item ID that keeps a transaction in the CIP and Business Central linked together. ‘Processing Count’ shows how many times a message has been processed. A failed message will top at 5 and then be ignored. ‘Document ID’ is used by some functions to keep track on a second reference. ’Related Document ID’ is used by some functions to keep track on a third reference. ‘Message ready to be processed’. If this is unchecked it means that the message will not be processed. ‘Message received’. If this is unchecked it means that the message has not yet been processed. ## Extras {% hint style="info" %} More information on this subject can be found in our ['Core Concepts'/'GEDI Message Queue'](/standard-app-core-concepts/concepts/gedi-messages-queue). {% endhint %} ## Re-run 'GEDI Message' Sometimes it is necessary to reset a message to run it again. For example if an invoice needs to be resent. ### Instructions * In Business Central search and go to ‘GEDI Message Queue’. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FZXBE7F1NILSxFARefmPo%2Fimage.png?alt=media\&token=76e7359a-a336-4d4e-b36b-9f5a5a783172) * Click 'Search' and search for messages related to the message you need to re-run. To find an invoice search by invoice number and the page will show you messages related to that invoice number. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fg38AXdgrAsBHeuhVnhUA%2Fimage.png?alt=media\&token=33731448-1364-42e3-ae37-03fffd01f1eb) * Find the message you like to re-run. You do that by looking for the correct ‘GEDI Message Code’. For example, to resend an invoice look for SI-02-RQ. That is the 'GEDI Message Code' to request the extraction of invoice information. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FLhAxTcD46825hsE4Xo1z%2Fimage.png?alt=media\&token=8210587e-248b-46ed-8f6f-0157f044193a) {% hint style="info" %} A list of what message codes the Golden EDI setup use can be found in ‘GEDI Messages Codes’ in Business Central. {% endhint %} * Once you have found the correct 'GEDI Message Code', select that line and press ‘Process’ and ‘Reset for new run’. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FacvsIYjsmjcjZ5WxQ22C%2Fimage.png?alt=media\&token=adc5a5ac-7b11-4bb5-93c1-e423d8e57e34) The 'Message Received' checkbox is now unchecked meaning that the message will be processed next time the 'GEDIQUEUE' job que entry runs. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FUhYD30vhW4vgQRX8qcKX%2Fimage.png?alt=media\&token=11c79ec0-aec9-43eb-9c72-61abc6a9685c) {% hint style="info" %} It is possible to force the message to be run directly by pressing 'Process' and 'Run Messages'. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FORt6kxuXfgba4YsGzZdm%2Fimage.png?alt=media\&token=02113b29-4334-4d45-a8e3-057de2b203ae) {% endhint %} When the SI-02-RQ message is processed the 'Message Received' is checked and the system has automatically generated the SI-03-EX holding the extracted data ready to be handled by the CIP. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fd3rgHcdeSFEJF7NNO0QJ%2Fimage.png?alt=media\&token=b7e9c2a3-023c-4b96-b3ac-9aa501516cea) Finally when the SI-03-EX is processed that message is updated with 'GEDI Message ID' and 'Message Received checked'. The invoice has now been resent to the CIP. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FjgSsW660zkEH0Qu27vqy%2Fimage.png?alt=media\&token=c0b4aeab-a020-43ce-9cc0-73c7c9b04429) ## Add new 'GEDI Message' Sometimes it is necessary to add a new message manually to the ‘GEDI Message Queue’. For example if you need to resend an invoice against a different 'GEDI Profile'. Or if an invoice earlier sent by mail shall now be sent via EDI. ### Instructions * In Business Central search and go to ‘GEDI Message Queue’. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FfuRlytIpEL1nFAIk4w2n%2Fimage.png?alt=media\&token=ad914c7c-3c84-4b60-8ad3-93e9e94dda50) * Click New to add a new entry. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FtGUaTV7rJ8vHSAsBHXNh%2Fimage.png?alt=media\&token=fae7ab96-61ea-4a42-b194-ae7e7b86498d) Move to ‘Message Code’ and add the 'GEDI Message Code' you like to run. For Example to request an EDI-invoice to be sent add code SI-02-RQ. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FYhB8E3VJKs6GTz87mRsW%2Fimage.png?alt=media\&token=1567c26a-647a-4b5b-9ce4-2e0fd8cd659e) {% hint style="info" %} A list of what message codes the Golden EDI setup use can be found in 'Standards'/'GEDI Codes’ {% endhint %} * Move to ‘GEDI profile’ and add the profile that should be used for the message. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FoR04UpjUIPyOGWfOCtX8%2Fimage.png?alt=media\&token=da6214c2-ded7-4951-b20c-910f27abfa89) * In ‘Message ID’ add the invoice number. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FSnhisdghG0FaxwNUD2Z5%2Fimage.png?alt=media\&token=9c349bec-4cfa-4c9f-92fe-fcb4f538bc0a) * Move to ‘Message ready to Process’ and check the checkbox. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FR0EyHuBXuNdb6LiP09OG%2Fimage.png?alt=media\&token=c05990ba-45e6-46f6-8966-1a8b421552a6) Now you have added a 'GEDI Message' to request an EDI-invoice. When the request is processed by the job queue entry another 'GEDI Message' with code SI-03-EX will be automatically added and then processed. ## Next Step Next step is to learn a bit about the 'GEDI Status Codes' # GEDI Status Codes The 'GEDI Status' gives information about a 'GEDI Message's' current status. ## Introduction In the 'GEDI Status Codes' page view in Business Central you will find 'GEDI Status Codes'. The 'GEDI Status Code' is connected to a 'GEDI Message Code'. When a 'GEDI Message' is created or executed, depending on the configuration, a 'GEDI Status' will be created. The 'GEDI Status Codes' page view shows the configured status codes with Code, Description, Code Next Step Suceeded / Failed and Status Color Scheme. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FuBChMatdWVZZbGiNds1w%2Fimage.png?alt=media\&token=a0d9c00a-bf2d-4e87-b52d-7ebf11021a4d) ## Extras {% hint style="info" %} More information on this subject can be found in our ['Core Concepts'/'GEDI Status Codes'](/standard-app-core-concepts/concepts/gedi-status-codes). A complete list of standard 'GEDI Status Codes' can be found in ['Standards](broken://spaces/Qs8RQAUXhZJLqyRtzHNZ/pages/u5c19pBh1QYNU3HT9DSO)'/'GEDI Codes'. {% endhint %} ## GEDI Status in Business Central The GEDI Status can be found in different places in Business Central. In sales documents such as 'Sales Order' and 'Sales Invoice' under section 'Invoice Details' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FRTIitIsGmEMxe4k26gx7%2Fimage.png?alt=media\&token=c148797b-35df-4060-92bc-c72dc9c05b29) In 'Posted Sales Invoice' under section 'Shipping and Billing' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FC53isn449wIeIQc4r9GR%2Fimage.png?alt=media\&token=81d9bb91-232a-4ce4-a78e-7b95cc2eb93a) In list views such as Posted Sales Invoices, Posted Sales Shipments etc. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FndTUmrC7QctsfR5UZjoj%2Fimage.png?alt=media\&token=6e2a03de-bb55-4c2a-b8c2-a7b77b1c82fe) There are also GEDI Specific list views in Business Central where you can see the status. 'GEDI Posted Sales Invoices', 'GEDI Posted, Sales Shipments' etc. The benefit of using the GEDI specific lists are that they are already filtered by documents that have been processed via Golden EDI instead of showing all records. Also, they are showing the 'GEDI status' according to the defined color scheme. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FpBElexSUD9cw6DgeUMko%2Fimage.png?alt=media\&token=8b39afa8-12d3-4abf-bd54-5100566ea4e7) In 'GEDI Status Ledger' you are able to find how the status have changed for each document. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FBrrJUXXsehxinZ8r0BO6%2Fimage.png?alt=media\&token=1bb1d496-3a4f-45ba-b293-69d6e30631c3) {% hint style="info" %} It is possible to translate the 'GEDI Status Code Description' for example to be presented in company internal language. {% endhint %} ## Next step Next and final step in the Beginner Courses part of the Implementation Academy is to learn about the 'CIP Customer View'. # CIP Customer View ## Introduction All Golden EDI customers can request a login to the customer view in the Cloud Integration Platform (CIP). In the CIP customer view our customers can see their outgoing and incoming messages with a log for each message. It is also possible to see both the original and translated data received to, and sent from the CIP. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FJ02tlVWJsqq82vaQe85b%2Fimage.png?alt=media\&token=27ae34db-2ce9-4ae6-8e04-931acdffc5da) Log in to the CIP via [portal.goldenedi.com](https://portal.goldenedi.com) and the login information received from Golden EDI. ## Extras {% hint style="info" %} More information on this subject can be found in our ['Core Concepts'/'Cloud Integration Platform'](/standard-app-core-concepts/concepts/cloud-integration-platform). {% endhint %} ## CIP Dashboard When you login you will access the dashboard. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Flv2MigCAiujJJBq0Ge4z%2Fimage.png?alt=media\&token=6fbff3d7-3f11-4603-8821-f106899e47b8) On the left hand side of the dashboard you see information about your Business Central partner, your organization name, time zone and your name. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Frb8W1uHTNenCt9X7fcAN%2Fimage.png?alt=media\&token=befcb6f9-a2b6-4e30-aea0-33f0db3fd370) Further down on the left hand side you find shortcuts to access the different pages in the CIP. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FSuExB174Zl7D79ksVbkc%2Fimage.png?alt=media\&token=82b1c457-a3a3-49f9-ae70-4ed5d74dcc76) 'Dashboard' will take you back to the dashboard. 'Incoming queue' will take you to the view of all incoming Work Items. Please note, if you have access to multiple organizations you must first select what organization you like to review. 'Outgoing queue' will take you to the view of all outgoing WorkItems. Please note, if you have access to multiple organizations you must first select what organization you like to review. 'Search' will open up a page where you can do a search among parties available in specific VAN networks. 'Monitoring' will give you a view over the status for the communication between the CIP and Business Central. 'Organization' is only visible when you have access to more than one organization. This is where you choose what organization you like to view. The rest, and main part, of the dashboard gives you information about eventual queue problems. The queue is divided into Outgoing WorkItems and Incoming WorkItems. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F2Xoign9J4eqL9wCxRv7Z%2Fimage.png?alt=media\&token=ec156206-ec72-4459-8a62-0c38c09b2916) And further down below the queue problems the dashbaord also include some WorkItem statistics. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FroemGYkHP6Us0bLcVgvp%2Fimage.png?alt=media\&token=793c4872-3540-4e36-bb49-84532d68406f) ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FzKKhyi5KT9thvjDMPV7A%2Fimage.png?alt=media\&token=a3986dfa-59b0-4eb9-81f4-541c6d45e17f) ## Incoming/Outgoing Queue The 'Incoming Queue' view and the 'Outgoing Queue' view are equally structured. Each WorkItem is presented in a number of columns. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FqiRVHgjXFIcRsIrNl5PI%2Fimage.png?alt=media\&token=695024dd-a080-44c1-989a-98551ca0bc6b) 'WorkItemId' is the unique Id of ths specific transaction. This 'WorkItemID' is the connection to the specific 'GEDI Message' in Business Central. 'Status' shows the status of the transaction. 'Pending' for transactions not yet complete. 'Completed' for succesful transactions or 'Error' for transactions that have resulted in some kind of failure. 'Number' is the document number. For outgoing Invoices this is the invoice number, for incoming order this is the sending party ordernumber etc. 'Connection ID' is the Connection ID that is used for this specific WorkItem. One organization can have multiple connections. 'Created time' is the date and time when the WorkItem was created in the CIP. 'Completed time' is the date and time when the WorkItem was succesfully completed. 'Meta Data' gives information of the type of transaction. Invoice, Order, Order Confirmation etc. 'Retry Count' counted up for each time the CIP are trying to complete the transaction. This will top at 20 before a WorkItem is failed. 'Info' holds additional information as for example a pdf icon if a pdf is enclosed in the message or a wrench if the WorkItem is sent in testing purpose. The search field up in the right hand corner is a powerful possibility to search for specific WorkItems by any of the columnvalues. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FALcyQjunPkWnBRhNFNyh%2Fimage.png?alt=media\&token=be591e65-27e9-4012-ab69-216fdd8273f0) ## WorkItem Details Each WorkItem can be reviewed in detail. * Click on 'Details' in the right end of the WorkItem line in the Incoming/Outgoing Queue ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FMwnvUnxSxtQ250qbIq5l%2Fimage.png?alt=media\&token=1e37e6a2-e81f-44c9-a5a5-52bd2bbc23c5) In the Details view you see the same information as in the Queue view. And as addition to that you also see the 'Filename' wich is the name of the file received or sent out. Also you have the 'ERP ID' wich is the related entry number in the 'GEDI Message Queue' in Business Central. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FWMtfr8VwMp7pNJRP3Vya%2Fimage.png?alt=media\&token=8a257ad0-80e4-4853-8331-5f3e976b2d35) On the left hand side of the Details view you have a number of Actions available. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F0aRh0LK7C46O23N8wplN%2Fimage.png?alt=media\&token=2860a873-a3c1-4e0f-972c-868f68c44e5f) 'View Log' will present you with a detailed log of the transaction. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FnEW6XxeqmJopNlJ6ILeS%2Fimage.png?alt=media\&token=885ac03c-e9d9-4a63-9c36-51e1fe159ae0) 'View EDI data' will show the actual EDI data received or sent out. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fs6Rfju7UsYtx4U4Sq3iN%2Fimage.png?alt=media\&token=83e8910e-f905-4fe2-8bf1-0c1b90196d3e) 'Download EDI' will download the EDI data as an XML file to your computer. 'Download PDF' will download the eventually enclosed pdf to your computer. ## Party Search To search for parties in specific VAN network directories press 'Search' in the CIP dashboard. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FbiCOMpImUibPRPo2ZFKK%2Fimage.png?alt=media\&token=ae996819-d2ba-4746-8ace-1868b82d2e82) Search by any of the identifiers Organization Number, VAT Identification Number or GLN. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2F24AXxnaRbKndFrOMzfYG%2Fimage.png?alt=media\&token=7308dfe1-6b0f-468b-90d8-f3b6187f3444) The result will show wether the party exists and if they accept EDI transactions. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FnjKNRaXr0hvbcNRihwtn%2Fimage.png?alt=media\&token=b64b9bd0-0729-493e-be79-802501ba7cfa) ## Organization Details Under your Organizations name in the CIP you can 'Click for details' ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2FnoGtyqNr2CnK55XzcVqx%2Fimage.png?alt=media\&token=a52c2a25-6d91-4c8a-bde8-1ac508562e7a) Here you will se the Organization details that Golden EDI has about your company. If you have the Organization Admin role you will be able to update the organization data. ![](https://2265956547-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFEfalHvEWA6QmvEniWuJ%2Fuploads%2Fb4E3vdLD2qfMKaOGqKJh%2Fimage.png?alt=media\&token=c28d0cf2-9f03-4aff-ae26-59e4601265f7) {% hint style="warning" %} It is important that the contact information, especially the E-mail for EDI issues, are correct since that address will be used to send out important notifications from the CIP team. {% endhint %} # Congratulations! You have now finished our Beginner Courses and hopefully you have gained knowledge enough to feel confident in Installing Golden EDI Standard App and do the necessary, beginner configurations. # Courses {% content-ref url="/spaces/xwncnNzHcS0rO9lJ3q5R" %} [Courses](https://docs.goldenedi.com/courses/) {% endcontent-ref %} # Implementation Academy Click the link to go back to Implementation Academy Welcome Page {% content-ref url="/spaces/5j3ssU7KCYI19mOdXAqF" %} [Implementation Academy](https://docs.goldenedi.com/) {% endcontent-ref %} # Guides Collection ## Prepacked Setups in GEDI Setup Catalog {% content-ref url="/spaces/-M64fo8oEu5prbfhnsa-" %} [Freemium](https://docs.goldenedi.com/freemium/) {% endcontent-ref %} {% content-ref url="/spaces/-M2ldF5Ogu5xZEyXimzB" %} [Basic Invoice](https://docs.goldenedi.com/basic-invoice/) {% endcontent-ref %} ## Standards {% content-ref url="/spaces/Qs8RQAUXhZJLqyRtzHNZ" %} [Standards](https://docs.goldenedi.com/standards/) {% endcontent-ref %} # Freemium - Golden EDI Freemium - A Product setup for Golden EDI app on Appsource for Business Central {% embed url="" %} For more information about Golden EDI and what we do, please visit our website. {% endembed %} ## Introduction to Freemium Golden EDI - Freemium adds powerful functionality that will make your invoicing process more streamlined. Golden EDI - Freemium allows you to setup the ‘Customer Card’, to automatically send out PDF invoices and credit memos via e-mail when ‘Posting’ them. This means you don’t have to manage them one by one, which is ineffective and time consuming. * Choose ‘GEDI Profile’ on ‘Customer Card’ to activate functionalities. * In ‘Posted Sales Invoices/Credit memos’ you’ll find an overview of ‘GEDI Status’ of the Invoice. * ‘GEDI Message queue’ gives traceability on all PDFs generated and allows reprocessing. * ‘Job Queue Entries’ processes the messages separately in the background, as scheduled. * PDF [Order Confirmation](/freemium/pdf-order-confirmation/untitled) can be activated if needed. ### Freemium - Product Information * Available for Business Central Cloud via [Microsoft AppSource](https://appsource.microsoft.com/en-in/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9) * Supports E-mail PDF Invoices via your own SMTP. * Possibility to enable PDF Order Confirmation via your own SMTP. * Free to use! No installation or transaction fees. {% hint style="warning" %} **Do you want to send e-invoices also?** Our App can handle that for you as well.\ Please see our other products '[Basic Invoice'](https://docs.goldenedi.com/basic-invoice/introduction-to-basic-invoice) and '[Advanced Invoice](https://docs.goldenedi.com/basic-invoice/uppgrade-to-advanced-invoice)' for more info! {% endhint %} It is also possible to customize the PDF functionalities further, for example adding Invoice Reminders or adding other attachments to the emails. Please contact to get help with this. {% embed url="" %} If any questions, please visit our support section on our website. {% endembed %}
If you have already installed Freemium, you can jump directly to the User Guide bellow. {% content-ref url="/pages/-M64mdqMh\_TPXAabkAIe" %} [USER GUIDE](/freemium/user-guide/customers) {% endcontent-ref %} This guide will help you how to initialize, setup and use Golden EDI Freemium functionality that will support you to automatize your invoice process. # Installing Install the app from Microsoft AppSource ## Prerequisites First you need to make sure that following prerequisites are fulfilled in order to install & setup the app: * License type for your user is a Full User. * Your permissions are set to 'SUPER' or equal. * Make sure you have permission to install Apps to your Business Central environment. * Set your Role Center to 'Business Manager'. So that you get the correct privileges to run the initialization of Golden EDI. {% hint style="danger" %} This documentation is made for Golden EDI app version 3.1.1.0 or higher. If you already have a lower version of our app, you need to uninstall it and re-download it from AppSource {% endhint %} ## Install Golden EDI from AppSource * Go to [Golden EDI](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9) app on the Microsoft AppSource. * Click 'FREE TRIAL' under the logo to install the app: ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lvlorJ3aUNYLHjLoA%2Fbild.png?alt=media\&token=2e13bf30-c13b-493a-b27e-3a02af7d2473) * You may be prompted to login to your Microsoft Office 365 account, do so if that option comes up. * Fill out your contact information and accept terms, then click on Continue. * Choose the environment where the app should be installed, most likely your production environment. ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lwziPqjPqJ3DwoixB%2Fbild.png?alt=media\&token=bf0b61b8-d5c4-416f-813f-91390c074213) * Now it will install the app automatically in the background. * In Business Central, if you go to page 'Extension Management' you can see the status. After a few minutes the Golden EDI app should say "Installed" when it's done. ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lxxxAfXZcRIZSXnu7%2Fbild.png?alt=media\&token=e2fd6257-e7a1-41e5-ba2d-4287fd5c4358) * When it is installed you can move on to the next page # Outgoing Email Choose your Outgoing Email configuration {% hint style="danger" %} In Business Central version 18 and later, a new feature for outgoing email was added called '**Email Accounts**'. {% endhint %} We recommend that you use the new way of setting up e-mail via '**Email Accounts**' when setting up a new GEDI Freemium. Both '**Email accounts**' and '**SMTP Mail Setup**' is compatible with GEDI Freemium.\ '**Email Accounts**" have priority if your environment have both configured. '**Email Accounts**' have more functionality build into Business Central in Standard, and GEDI Freemium can take full advantage of these new functionalities. New advantages of using '**Email Accounts**' is for example; * Possibility to setup multiple outgoing e-mail accounts. * Adding scenarios, using different outgoing e-mails per document type. * Overview in Business Central of email sent out as well as preview of them. * Easier setup of MS 365 Shared mailboxes. * Reply or forward a already sent e-mail using the inbuilt preview of the email. Please contact your Business Central partner for more information about added advantaged of using '**Email Accounts**'. ## Check if 'Email Accounts' is enabled (On-Prem BC18 only) {% hint style="warning" %} In Business Central 19 update later 2021 Q4, Email Accounts will be enabled as standard. {% endhint %} * In Business Central, search and to go 'Feature Management'. * Check if the row *"Feature Update: Enhanced email capabilities*" is enabled or disabled. * This feature needs to be enabled if you want to setup '**Email Accounts**'. {% hint style="danger" %} Contact your Business Central Partner and analyze consequences before enabling this yourself! {% endhint %} ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-MbKrm9zgEz23H33g1BD%2F-MbL5fsOwPR6fAM2N7CJ%2Fbild.png?alt=media\&token=ab1bf083-8517-4e34-b3d6-5317d6c31cde) If this feature is Enabled, go to '**Email Accounts**' page bellow to configure this. {% content-ref url="/pages/-MbL0tfAV10GB0Cw4J6\_" %} [Email Accounts](/freemium/installation-guide/smtp/email-accounts) {% endcontent-ref %} If this feature is Disabled, go to '**SMTP Mail Setup**' page bellow to configure this. {% content-ref url="/pages/-MbL13gfb6ZdjL-guKwN" %} [SMTP Mail Setup](/freemium/installation-guide/smtp/smtp-mail-setup) {% endcontent-ref %} Or if you already have either mail setup in your Business Central environment, you can move on to Initialize instead. {% content-ref url="/pages/-M64qeocxHhJmdyte\_X1" %} [Initialize](/freemium/installation-guide/initialize) {% endcontent-ref %} ## # Email Accounts {% hint style="danger" %} Either run the guide for '**Email Accounts'** or '**SMTP Mail Setup'**, you don't need both! *'Feature Update: Enhanced email capabilities'* needs to be **enabled** in feature management for you to find the assisted setup bellow. {% endhint %} ## Setup E-mail via "Email Accounts" * In Business Central, search and go to the page 'Assisted Setup' * In 'Assisted Setup', click on 'Set up outgoing email' if its not already Completed.\ (If this is already Completed, you can jump to the '[Initialize](/freemium/installation-guide/initialize)' page) ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M64rg7gmOKMQgNMseAp%2Fbild.png?alt=media\&token=4942439f-266f-4d25-b1a4-41bcd9723d03) * Select the email type and progress the assisted guide as instructed in the pop-ups. ![Email account options to configure](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-MbKrm9zgEz23H33g1BD%2F-MbLAPVfCYR6WBDo__1I%2Fbild.png?alt=media\&token=ea3223c8-24ea-49a6-889d-de08f53e9ddf) * Fill in the email account details and then click next when you are done. ![Example of Microsoft 365 Shared account settings](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-MbKrm9zgEz23H33g1BD%2F-MbL98SC9UjF8H44Fj4E%2Fbild.png?alt=media\&token=dca91ad5-c3ee-4158-965c-4b793a4c7bf1) ![Example if SMTP account settings](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-MbKrm9zgEz23H33g1BD%2F-MbLA8rP-PyAQ3nfPqTX%2Fbild.png?alt=media\&token=a4ae33c2-f663-4e36-bd31-90ade56dc876) {% hint style="danger" %} If you choose to run Microsoft 365 shared mailbox, the BC user who runs the GEDIQUEUE job queue later, needs to have e-mail rights configured for the outgoing e-mail address. {% endhint %} * Finish the assisted setup. If you need to verify your settings, you can click ‘Send Test Email’ in the assisted guide itself and check if it works. If not, you can go back and check the entered details. {% hint style="warning" %} If you have problems setting up your SMTP, please contact your Business Central partner to help you with this. {% endhint %} Move on to 'Initialize' when you have a working outgoing e-mail. {% content-ref url="/pages/-M64qeocxHhJmdyte\_X1" %} [Initialize](/freemium/installation-guide/initialize) {% endcontent-ref %} # SMTP Mail Setup {% hint style="danger" %} Either run the guide for "**Email Accounts**" or "**SMTP Mail Setup**", you don't need both! *"Feature Update: Enhanced email capabilities"* needs to be **disabled** in feature management for you to find the assisted setup bellow. {% endhint %} ## Setup E-mail via "SMTP Mail Setup" * In Business Central, search and go to the page 'Assisted Setup' * In 'Assisted Setup', click on 'Set up outgoing email' if its not already Completed.\ (If this is already Completed, you can jump to the '[Initialize](/freemium/installation-guide/initialize)' page) ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M64rg7gmOKMQgNMseAp%2Fbild.png?alt=media\&token=4942439f-266f-4d25-b1a4-41bcd9723d03) * Select the email provider, pictured will be a set-up of ‘Other Email Provider’ using SMTP. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M64sEtP2kMeNk7Q5JMT%2Fbild.png?alt=media\&token=2d0933f1-0b7b-4dd9-a9d1-3f242a9c56b1) * Fill in the email account details and then click next when you are done. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M64sb0a05mlYf809E2I%2Fbild.png?alt=media\&token=b0432e2b-c39f-4eec-a910-ab896cc3bfb5) * Click finish to complete the set-up of E-mail communication. If you need to verify your settings, you can click ‘Send Test Email’ and check if it works. If not, you can go back and check the entered details. {% hint style="warning" %} If you have problems setting up your SMTP, please contact your BC partner to help you with this. {% endhint %} Move on to 'Initialize' when you have a working outgoing e-mail. # Initialize Initialize the app via a assisted setup * In Business Central, search and go to the page 'Assisted Setup' * In 'Assisted Setup', click on 'Golden EDI - Initialize'. {% hint style="success" %} If you already completed "Golden EDI - Initialize" in another of our products on this version of the App, you don't need to to it again. If so, jump to the "[Freemium](/freemium/installation-guide/freemium)" section. {% endhint %} ![Search on "Golden EDI" to find it easier](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M64zIsihYbCD7RlwLLu%2Fbild.png?alt=media\&token=3c11cd7b-50c9-4e62-b5f8-f36da5cfe6e4) * Accept the Terms of Use and Privacy Policy by clicking the checkbox and then Next. You can find both the privacy policy and the terms of use on the [AppSource](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9). ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m1Vrr6ZpJELMut9z9%2Fbild.png?alt=media\&token=9d4f5b74-e530-4ff2-b450-ba7cce62a647) * At the next page click on 'Next' to download and import base data necessary for Golden EDI. The download will not take more than a few seconds to complete. ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m1wQHEXpLO4FzSJq1%2Fbild.png?alt=media\&token=31b749a2-a710-4eeb-9074-588a606076c4) * Close the first assisted setup by clicking done. ![](https://gblobscdn.gitbook.com/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m2LA481X_NO8BQZ0t%2Fbild.png?alt=media\&token=9d957912-c72b-4c33-b20e-8bf5b2a7116e) # Freemium Configure Freemium via a assisted setup * In Business Central, search and go to the page 'Assisted Setup'. * In 'Assisted Setup', click on 'Golden EDI – PDF Invoicing Setup'. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M65-ozc_jp7ZQ3F-ZE3%2Fbild.png?alt=media\&token=7d5fd4a1-6bc7-498c-9549-827e19da125d) * At the first screen you can read through the information and then click next when you are ready. It will start downloading and importing the configuration for PDF invoicing. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M65-ycjb_RJpoc80Dde%2Fbild.png?alt=media\&token=b4b4cb57-5c45-4a37-8c05-7726d433ad13) * When it’s done you will be taken to the next screen where you can fill out both the “From Address” used when sending the invoices/credit-memos and the language used when generating the text in the e-mails. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M65049gOTr7TifS7FXO%2Fbild.png?alt=media\&token=07727b71-a0fd-43fb-a728-866d43bd225b) ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M64oJNiA3nJhaBskvG-%2F-M650JMXR3QUB41gIgNC%2Fbild.png?alt=media\&token=d18e1621-c147-4141-8535-cec94de9df4a) When all 3 assisted setups are done, you can move on to the next page to run a test case with your new functionalities in freemium, to make sure that it works correctly. {% content-ref url="/pages/-M650uxkA4W91xdgaCZy" %} [Test case](/freemium/installation-guide/test-case) {% endcontent-ref %} After the test case is done, the final step will be to create the the Job Queue Entries to activate the automation. {% content-ref url="/pages/-M6514r7Aa4U4UR4sg\_O" %} [Job Queue Entries](/freemium/installation-guide/job-queue-entries) {% endcontent-ref %} There is also the possibility to use assisted setup for 'Golden EDI - Customer Setup' to batch update the customers with GEDI profiles. {% content-ref url="/pages/-M651BUYdRYqOxHqAcIi" %} [Batch update customers](/freemium/installation-guide/batch-update-customers) {% endcontent-ref %} # Test case Run a test case to check that SMTP and app is configures correctly. First, setup 1 customer to test with according the the '[Customers](/freemium/user-guide/customers)' section in the 'User Guide'. {% hint style="danger" %} **IMPORTANT** - To be able to run this test you need a Sales Invoice that we will later 'Post'. If your using a real invoice for the test, put yourself as the email receiver first to confirm it works. {% endhint %} * In Business Central, search and go to the page "Sales Invoices" ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69-pH1-t-x8RgzDpbo%2F-M69Hu79wSWvH39T7Qo3%2Fbild.png?alt=media\&token=8be73ec4-322d-4024-9618-d7c40115b5c9) * Open the sales invoice that you want to run the test with. * Under the "Invoice Details" section, you will find the field 'GEDI Profile'. Change this to 'PDF-BC', in order to activate the functionality.
* 'Post' the invoice. * If you search and go to the page 'Posted Sales Invoice' you can find a column with 'GEDI Status' - this should now have status 'Requested'.
* Search and go to the page 'GEDI Message Queue'. * Here you will find a row with your invoice number in 'Message ID' column and with the 'Message Code' = 'SINV-81-MR', probably it's the last row in the list. * Mark the row, and go to 'Home' tab and click 'Run Message' to manually trigger the invoice.
* If you go back to 'Posted Sales Invoices' you can see that the GEDI Status is now 'Sent'
{% hint style="success" %} If you received the e-mail this means the test was successful and SMTP and customer configuration is correct. {% endhint %} {% hint style="warning" %} If you changed the customer email to your own address for the test, don't forget to set it back to the correct customer email! {% endhint %} During this test you manually processed the message via our 'GEDI Message Queue', in the next step we will create and schedule 'Job Queue Entries' to handle this for us automatically in the background. # Job Queue Entries Schedule the messages to automatically process In this section we will create 2 different Job Queue Entries, 'GEDIQUEUE' & 'GEDIDELETE'. 1. **GEDIQUEUE**: will be set on a 5min schedule, each workday between 07:00 & 20:00, and will process all new messages to the Cloud Service 2. **GEDIDELETE**: will be set once a day schedule, at 04:00, and will clean up old GEDI data no longer needed. {% hint style="danger" %} If you have multiple Golden EDI solutions combined in your Business Central Company, and you already have Job Queue Entries configured, you don't need to create new identical once!\ e.g. if 'GEDIDELETE' already exist, don't create another one. {% endhint %} * In Business Central, search and go to the page 'Job Queue Entries' ### GEDIQUEUE - Job Queue Entry Card * Click new to create a new 'Job Queue Entry Card' ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69L8Hm7uZqDSCbDjt9%2F-M69T3ooNz_7TXbzOLn_%2Fbild.png?alt=media\&token=f1717232-d8f3-4899-b0e3-287fb91904aa) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. * Fill in the 'Job Queue Entry Card' for 'GEDIQUEUE' as per screenshot or list bellow. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M64fo8oEu5prbfhnsa-%2Fuploads%2Fo74CFjJPNUXD2VCrs7Gr%2Ffile.jpeg?alt=media) #### General Section: | Field | Value | | ----------------------- | ------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019001** | | Job Queue Category Code | **GEDIQUEUE** | #### Recurrence Section: | Field | Value | | --------------------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 0700 | | Ending Time | 2000 | | No. Of Minutes between Runs | 5 | {% hint style="warning" %} If you have combined our 'Freemium' product with 'Advanced invoice' or another custom made EDI solution using our app, then additional settings on the GEDIQUEUE should be set to enable Heartbeats. Heartbeats should not be active if you only run 'Freemium' or 'Basic Invoice' 'GEDI Run Heartbeat to Golden EDI' - set to 'Checked'\ 'GEDI Run Heartbeat w. GEDI Profile - choose 'INTERNAL' {% endhint %} ![If other Golden EDI solutions should run Heartbeats on the GEDIQUEUE](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69L8Hm7uZqDSCbDjt9%2F-M69V76a-U9_i5DIE-pt%2Fbild.png?alt=media\&token=24a9c19c-b70f-40c5-bf68-20a41f5215da) * The 'GEDIQUEUE' 'Job Queue Entry' is now setup to processing the EDI messages automatically every 5min, each workday between 07:00 and 20:00 * Close the Pop-up and **don't restart the job queue yet.** ### GEDIDELETE - Job Queue Entry Car * Click new to create a new 'Job Queue Entry Card' ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69L8Hm7uZqDSCbDjt9%2F-M69T3ooNz_7TXbzOLn_%2Fbild.png?alt=media\&token=f1717232-d8f3-4899-b0e3-287fb91904aa) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. * Fill in the 'Job Queue Entry Card' for 'GEDIDELETE' as Screenshot or list bellow. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M64fo8oEu5prbfhnsa-%2Fuploads%2FQohn2QDvrPzOOSgV6vtW%2Ffile.jpeg?alt=media) #### General Section: | Field | Value | | ----------------------- | -------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019006** | | Job Queue Category Code | **GEDIDELETE** | #### Recurrence Section: | Field | Value | | ----------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 0400 | * The 'GEDIDELETE' 'Job Queue Entry' is now now setup to clean up old GEDI data no longer used once a day at 04:00. * Close the Pop-up and **don't restart the job queue yet.** {% hint style="success" %} Golden EDI - Basic Invoice are now configured in your Business Central! {% endhint %} The next step will be to update the relevant customers with the 'GEDI Profile' and the correct e-invoice configurations. More on how to do this under **User Guide - Customers**. {% content-ref url="/pages/-M690O\_qAhqxDPPhYMcA" %} [Customers](/freemium/user-guide/customers) {% endcontent-ref %} Once you have went thru the **User Guide - Customers** to understand how to correctly configure them for e-invoicing, you can also use our assisted setup for batch updating the relevant customers much faster. {% content-ref url="/pages/-M651BUYdRYqOxHqAcIi" %} [Batch update customers](/freemium/installation-guide/batch-update-customers) {% endcontent-ref %} # Batch update customers After you have went thru the **User Guide - Customers** to understand how to correctly configure customer cards for e-invoicing, you can also use our assisted setup for batch updating the relevant customers much faster. {% content-ref url="/pages/-M690O\_qAhqxDPPhYMcA" %} [Customers](/freemium/user-guide/customers) {% endcontent-ref %} * In Business Central, search and go to the page 'Assisted Setup'. * In 'Assisted Setup', click on 'Golden EDI - customer Setup' ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69L8Hm7uZqDSCbDjt9%2F-M69XEz7o2sFJVxGvOWE%2Fbild.png?alt=media\&token=41376284-9aee-467c-bc97-40b363794a27) * Select the Profile you want to add in the selection box above the list. * In the list of customers bellow, select the customer row that you want to add the profile to and click the button '**Set GEDI Profile'.** * You should now see profile you selected in the GEDI Profile column. * In the Email column, you can see and change the standard e-mail from the customer card. * If you want to setup Document layouts for the customer, type in the correct report IDs in columns 'Invoice Report' and 'Credit Report'. When you do this, document layouts row will be created on the customer using the standard email address from the customer. * You can see the Document layouts created if you select the customer and press "Document Layout" button at the lower right. Then you can also change the email, if you want another receiver than the standard email. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69L8Hm7uZqDSCbDjt9%2F-M69ZlWAIqRd1bBx_PdF%2Fbild.png?alt=media\&token=bee12dbf-edc2-44bd-a345-fa04b5585372) {% hint style="info" %} 'GLN' column is not used for 'Freemium' {% endhint %} # Go-live Before you go-live, you should have done these steps; * Configures business Central according to the guide. * Made a test case to make sure you are sending out emails with PDFs correctly. * Updated the customer cards according to the guide. * **Optional -** [Enable Order Confirmations](/freemium/pdf-order-confirmation/untitled) to be sent out via email PDFs. If all of above is done, and you are ready to go-live, go back to 'Job Queue Entries' in Business Central and **restart** the '**GEDIQUEUE**' and '**GEDIDELETE**' job queues to start processing queued messages in our app. {% hint style="info" %} If you for some reason wants to stop or pause the automatic processing in the future, you should set 'Job Queue Entry' 'GEDIQUEUE' and 'GEDIDELETE' to 'Set On Hold'. You can restart it whenever you want to enable it again. {% endhint %} {% hint style="danger" %} The user that restarts the Job Queue Entry must have user permissation set 'SUPER' or 'GEDI ADMIN FULL'. {% endhint %} Follow up on your first invoices after this and make sure their GEDI status reaches 'PDF Sent', as described in the [invoice process.](/freemium/user-guide/invoice-process) # Customers * In Business Central, search and go to the page 'Customers'. ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69-pH1-t-x8RgzDpbo%2F-M690zP8GjNO-8irbs06%2Fbild.png?alt=media\&token=65a5c0a5-b9fd-4623-a7a3-4846065cd5df) * Open up the customer card that you want to enable Basic Invoice for. * Under the 'Invoicing' section you will find the '**GEDI Profile**' to activate the functionalities for the customer, change the GEDI Profile to 'PDF-BC'. There is 2 ways to configure which e-mail address the Invoice should be sent to, Document layouts and standard e-mail contact. * If Document layouts are filled in, this has a higher priority and the PDF will be sent to this e-mail.\ Document layouts have the added benefit of allowing more customization on the customer. * If Document layouts are not filled in, it will be sent instead to the e-mail contact on the customer card (18|102) . In this case your standard defined Invoice PDF report will always be used and Invoice, Credit and Order Confirmation will be sent to the same e-mail contact on the customer card. {% hint style="danger" %} If neither of these 2 are filled in, the PDF e-mail will not be sent out! {% endhint %} ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M69-pH1-t-x8RgzDpbo%2F-M699zII_ASnU7MHDoOc%2Fbild.png?alt=media\&token=c0ea6fd0-b435-456c-98b1-c893e0a1497c) **If you want to use document layouts;** * Still in the customer card, go to 'Navigate' in the header bar, and click on 'Document layouts'. * Create 2 rows here according to this table (3 rows if you use [enabled order confirmation](/freemium/pdf-order-confirmation/untitled)): | Usage | Report ID | Send to Email | | -------------------- | ----------------------------------------- | -------------------------------------- | | **Invoice** | The report you use for invoices | The receiver of invoice | | **Credit Memo** | The report you use for credit memos | The receiver of the credit memo | | *Order Confirmation* | The report you use for Order Confirmation | The receiver of the Order confirmation | {% hint style="info" %} If you are not sure which Reports to use, please contact your BC partner to help you with this. {% endhint %} ![](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-M6iE-txvT2rl5rGxZ0F%2F-M6iOY7O-3VH234xv_9v%2Fbild.png?alt=media\&token=240fd75d-ed88-47be-8e1e-a82d1ab0ae77) If you want to send the invoice to multiple email addresses, this can be done in document layouts using a ; as separator. E.g. m**;**e. It is also possible in the document layout to change the e-mail body that is sent out. This is done in selecting a 'Email Body Layout Description' and enable 'Use for email body'. It could be that you already have templates here to use. If you want to add new once, please contact your BC partner for this. If you have many customers to configure this way, we recommend you to use our batch update customers assisted setup. #### If you don't use document layouts; The standard defined report and email body text used in the case when not using document layouts, this is instead defined in the page "Report Selection - Sales", Usage: "Invoice" / "Credit Memo". ![Report Selection - Sales / Invoice](https://713365273-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M64fo8oEu5prbfhnsa-%2F-MIJZ3j8TFPKznBESvmY%2F-MIJZUd9hainOuqHt09h%2Fbild.png?alt=media\&token=314be795-bbaa-4ef0-ad44-8776a59b05eb) {% content-ref url="/pages/-M651BUYdRYqOxHqAcIi" %} [Batch update customers](/freemium/installation-guide/batch-update-customers) {% endcontent-ref %} # Invoice Process Now when the customer cards are configured correctly, we look at how the invoice process to send PDF email works with the Golden EDI app. When a sales order, invoice or credit note is created, it will inherit the 'GEDI profile' from the customer cards that we have configured. The GEDI profile will activate the freemium functions. {% hint style="warning" %} Before posting a sales invoice or credit note, it is possible to remove or change the 'GEDI profile' on it to override the customer cards for that specific sales invoice or credit note. {% endhint %} When you are trying to "post" a sales invoice or credit memo, the Golden EDI app will listen to this event and add it to the 'GEDI Message Queue' as an unprocessed message. {% hint style="info" %} At this point the '**GEDI Status'** for the posted sales invoice or credit note have been updated to '**Requested'**, letting you know that the message is queued. {% endhint %}
Every 5 minutes during normal business hours, a 'Job Queue Entry' is scheduled to process all unprocessed message in the 'GEDI Message Queue', at this point they will be sent out as emails via your SMTP. {% hint style="success" %} If the email was sent out successfully, the '**GEDI Status'** of the posted sales invoice or credit note will be updated to '**Sent**'. {% endhint %}
# Order Process Send out PDF Order Confirmations When the customer cards are configured correctly, and you have Enabled Order Confirmation, we can look at how the order process to send PDF email works with the Golden EDI app. When a sales order is created, it will inherit the 'GEDI profile' from the customer cards that we have configured. The GEDI profile will activate the freemium functions. {% hint style="warning" %} Before releasing or posting a sales order, it is possible to remove or change the 'GEDI profile' on it to override the customer cards for that specific sales order. {% endhint %} When you are trying to "release" or "post" a sales order, the Golden EDI app will listen to this event and add it to the 'GEDI Message Queue', and the Order Confirmation will be processed directly during the release of the order. (It will not wait for the 5min GEDIQUEUE). * If you released the Sales order, the '**GEDI Status'** have been updated to '**Sent (CFM)'**, letting you know that the message is sent. * If you posted the Sales order instead, it is now a Posted Sales Invoice, and you won't see this status. If the Order Confirmation for some reason failed, the posting should have stopped with an error. {% hint style="warning" %} In the second case, you can still check the 'GEDI Message Queue' to check if the Order Confirmation was sent out. In this case, search for the Sales Order nr in 'Message ID'. {% endhint %} # Enable Order Confirmation Freemium also includes the possibilty to send out PDF Order Confirmation via e-mail.\ This is disabled by default, but can be enabled following these steps; * In Business Central, search and go to the page 'GEDI Message Setup'. * In that table, you'll find 2 rows 'SORD-81-MR' and 'SORD-82-ME' * On these 2 rows, uncheck the checkbox in the column, 'Not Create Automaticall' * Now PDF Order Confirmation is enabled.
# Basic Invoice - Golden EDI Basic Invoice - A Product setup for Golden EDI on Appsource for Business Central {% embed url="" %} For more information about Golden EDI and what we do, please visit our website. {% endembed %} ## Introduction to Basic Invoice Golden EDI - Basic Invoice adds powerful functionality that will make your invoicing process more streamlined. Golden EDI - Basic Invoice allows you to setup the 'Customer Card', to automatically send out your invoices and credit memos electronically when 'Posting' them. This means you don’t have to manage them manually, which is ineffective and time consuming. * Choose 'GEDI Profile' on 'Customer Card' to activate functionalities. * In Posted Sales Invoices/Credit memos you’ll find an overview of 'GEDI Status' of the Invoice * 'GEDI Message queue' gives traceability on all invoices and credit-memos that has been generated and allows reprocessing. * 'Job Queue Entries' processes the messages separately in the background, as scheduled. ### Basic Invoice - Product Information * Available for Business Central Cloud via [Microsoft AppSource](https://appsource.microsoft.com/en-in/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9) * Supports E-invoices to receivers in the Sweden, Denmark and Finland. * Supports E-invoices using PEPPOL BIS Billing 3.0 using GLN as identifier. * Each Business Central company requires a separate license with Golden EDI * 3 Different Exchange types; EDI, PDF via E-mail or Paper Print * PDF layout for e-mail or print via Basic Invoice is standard format. * Invoice data sent according to GEDI standard template * Not able to send invoice attachments with the e-invoice * Doesn't require an extra user license in Business Central {% hint style="warning" %} If this doesn't match your business requirements, please check out our **Advanced Invoice,** that can be customized according to your business needs. {% endhint %} {% content-ref url="/pages/-M2loc3uv\_uHOxKpHY26" %} [Advanced Invoice](/basic-invoice/other/uppgrade-to-advanced-invoice) {% endcontent-ref %}
When downloading the Golden EDI App from the appsource, it's also prepacked with some free functionalities, such as automatically send out PDF invoices via e-mail/SMTP. Please read more about our "Freemium" on the [Appsource](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9?tab=Overview). {% embed url="" %} If any questions, please visit our support section on our website. {% endembed %} If you have already installed Basic Invoice, you can jump directly to the User Guide bellow. {% content-ref url="/pages/-M2lo\_VwOGL9CoiHNA3a" %} [User Guide](/basic-invoice/user-guide/customer-settings) {% endcontent-ref %} This guide will help you how to initialize, setup and use Golden EDIs Basic Invoice functionality that will support you to automatize your invoice process. # Register Register your company on our portal Before you can start setting up basic invoice as per this guide, you need to register your company on our [portal registration](https://portal.goldenedi.com/Registration/Register) page to get your license. After your have submitted your registration you will receive 2 e-mails from us: * **'Golden EDI - Next Steps'** - a short summery to guide your next steps and connection settings. * **'Document to e-sign'** - License agreement thru Scrive. {% hint style="danger" %} Basic Invoice requires a separate license with Golden EDI for each Business Central company. {% endhint %} Read thru the license agreement and sign it on Scrive before proceeding this guide to install the App. # Installing Install the app from Microsoft AppSource ## Prerequisites First you need to make sure that following prerequisites are fulfilled in order to install & setup the app: * License type for your user is a Full User. * Your permissions are set to 'SUPER' or equal. * Make sure you have permission to install Apps to your Business Central environment. * Set your Role Center to 'Business Manager'. So that you get the correct privileges to run the initialization of Golden EDI. {% hint style="danger" %} Golden EDI version 3.1.1.0 or higher is required for Basic Invoice. If you already have a lower version of our app, you need to uninstall it and re-download it from AppSource. {% endhint %} ## Install Golden EDI from AppSource * Go to [Golden EDI](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9) app on the Microsoft AppSource. * Click 'FREE TRIAL' under the logo to install the app: ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lvlorJ3aUNYLHjLoA%2Fbild.png?alt=media\&token=2e13bf30-c13b-493a-b27e-3a02af7d2473) * You may be prompted to login to your Microsoft Office 365 account, do so if that option comes up. * Fill out your contact information and accept terms, then click on Continue. * Choose the environment where the app should be installed, most likely your production environment. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lwziPqjPqJ3DwoixB%2Fbild.png?alt=media\&token=bf0b61b8-d5c4-416f-813f-91390c074213) * Now it will install the app automatically in the background. * In Business Central, if you go to page 'Extension Management' you can see the status. After a few minutes the Golden EDI app should say "Installed" when it's done. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2lxxxAfXZcRIZSXnu7%2Fbild.png?alt=media\&token=e2fd6257-e7a1-41e5-ba2d-4287fd5c4358) * When it is installed you can move on to the next page # Initialize Initialize the app via a assisted setup * In Business Central, search and go to the page 'Assisted Setup' * In 'Assisted Setup', click on 'Golden EDI - Initialize'. {% hint style="success" %} If you already completed "Golden EDI - Initialize" in another of our products on this version of the App, you don't need to to it again. If so, jump to the "[Basic Invoice](/basic-invoice/installation-guide/basic-invoice)" section. {% endhint %} ![Search on "Golden EDI" to find it easier](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3C8AWuXVBs_N1ZE8At%2Fbild.png?alt=media\&token=7195f94f-06e3-4261-8e9d-6a9133ffc11e) * Accept the Terms of Use and Privacy Policy by clicking the checkbox and then Next. You can find both the privacy policy and the terms of use on the [AppSource](https://appsource.microsoft.com/en-us/product/dynamics-365-business-central/PUBID.golden_edi%7CAID.goldenedi%7CPAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9). ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m1Vrr6ZpJELMut9z9%2Fbild.png?alt=media\&token=9d4f5b74-e530-4ff2-b450-ba7cce62a647) * At the next page click on 'Next' to download and import base data necessary for Golden EDI. The download will not take more than a few seconds to complete. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m1wQHEXpLO4FzSJq1%2Fbild.png?alt=media\&token=31b749a2-a710-4eeb-9074-588a606076c4) * Close the first assisted setup by clicking done. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m2LA481X_NO8BQZ0t%2Fbild.png?alt=media\&token=9d957912-c72b-4c33-b20e-8bf5b2a7116e) # Basic Invoice Configure Basic Invoice via a assisted setup * In Business Central, search and go to the page 'Assisted Setup'. * In 'Assisted Setup', click on 'Golden EDI - Basic Invoice Setup'. ![Search on "Golden EDI" to find it easier](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3C83fm3BrXhNxTsn3f%2Fbild.png?alt=media\&token=c563dc91-4b55-4be2-9392-b2bb461c0ae6) * Read thru the information in the popup and click 'next', to start download and import Basic Invoice necessary files. The download will not take more than a few seconds to complete. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m3hxHKU5bi-mXooKO%2Fbild.png?alt=media\&token=f334f97c-db0b-4e00-9744-9090332e7c31) * When it's done you will be taken to the next screen where you can fill in the conversion between your invoice units and standardized units for EDI. * The page will automatically find 'Units of Measure' defined in your Business Central. In the column 'Standard Code' you should fill in the corresponding EDI code for units used in invoicing, see list bellow. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m6hv7J-eJB01RI5nY%2Fbild.png?alt=media\&token=8bffaf81-2b34-4aea-8175-7c00817a0507) {% tabs %} {% tab title="EDI Standard Codes" %} | EDI Code | Description | | ------------- | ------------------------------------------------------------------------ | | **Piece** | Piece, the most common unit used. | | Undefined | Undefined | | Kilogram | Kilogram (KG) | | Litre | Litre (L) | | Milligram | Milligram (MG) | | Millilitre | Millilitre (ML) | | Millimetre | Millimetre (MM) | | Metre | Metre (M) | | SquareMetre | Square Metre (M^2) | | QubicMetre | Qubic Metre (M^3) | | MetricTon | Metric Ton | | Bundle | Bundle | | Box | Box / Number of Packs | | Gram | Gram (g) | | Centimetre | Centimetre (CM) | | Kilometre | Kilometre (KM) | | Day | Day | | Hour | Hour | | Month | Month | | Pallet | Pallet | | PalletEur6 | EUR 6 Pallet (800 X 600 mm). Also known as ISO 0 Pallet, 1/2 EUR Pallet. | | PalletEur | EUR Pallet (800 X 1200 mm). ISO 6780 ISO 1 Pallet. | | Bottle | Bottle, Non-Protected, Cylindrical | | Bucket | Bucket | | Pot | Pot | | Bag | XBG | | Roll | Roll | | Tray | Tray | | Pair | Pair | | Gigabyte | Gigabyte (GB) | | ServiceUnit | Service Unit | | {% endtab %} | | | {% endtabs %} | | * Click next when you are done. * Next step is to fill the conversion between your currency codes and standardized currency codes. * Usually in Business Central everything is pre-configured with the correct standard currency codes, but if it's not, you have here a chance to convert it to correct codes in EDI. Double check the currencies that you can invoice in, column 'Standard Code' is used for EDI. * Click next when you are done. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2m8qCImn4JqjtVSN4Y%2Fbild.png?alt=media\&token=c8a42699-370a-45b3-beb9-fa46e18252b9) * Read thru the information in the popup and click Finish. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2lq2Tx9xSVEQY6eTID%2F-M2mB7RNQB5dY3qZsm6M%2Fbild.png?alt=media\&token=d5861382-33f0-4fa7-a689-fe21e1abde00) # GEDI Profile Configure the connection to our Cloud Service * In Business Central, search and go to the page 'GEDI Profiles' * on the 3 profile rows 'BASIC-BBAN', 'BASIC-BGIR' and 'BASIC-IBAN', you need to fill in 'GEDI Connection Id' and 'GEDI API Key'. You should have received these in the '**Golden EDI - Next Steps'** e-mail when you registered your company on our cloud. The same Connection ID and API key is used for all 3 profiles. ![Screenshot from the Next Steps e-mail](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3BUKAAtdtxJv3iNpsj%2Fbild.png?alt=media\&token=0d89670b-a1dc-4f07-93ca-083a60d2798f) ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M5aTu6eIpI_UaCmdCOa%2F-M5aXdBXznAgmHNMdT6X%2Fbild.png?alt=media\&token=8069bb47-db2c-485b-87ed-59863aac005b) {% hint style="danger" %} IMPORTANT! - If you use multiple companies in your Business Central, each GEDI Connection ID and corresponding API key must be unique for each company. Each legal unit must have a individual license to send e-invoices! {% endhint %} {% hint style="info" %} The 3 profiles are setup to send different bank information that you want the payment of the invoice to be payed to, each customer needs to be setup with the correct payment type. The information is taken from "Company Information" page in BC. {% endhint %} | Description | GEDI Profile | Account from | Bank from | | -------------------------- | ------------ | ------------------------- | ------------------- | | Domestic Bank account | GEDI-BBAN | Bank Account No. (79\|14) | SWIFT Code (79\|39) | | Swedish Bankgiro | GEDI-BGIR | Giro No. (79\|11) | Always: 'BGABSESS' | | International Bank account | GEDI-IBAN | IBAN (79\|38) | SWIFT Code (79\|39) | ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M5fXey5Sxp366L-X1gv%2F-M5fYGo7TOILO5DSxjXZ%2Fbild.png?alt=media\&token=0e32d252-8a27-4980-9d1e-bc9ec936f955) When both assisted setups are done, and the profile is configured you can move on to the next page to run a test case with your new functionalities in Basic Invoice, to make sure that it works correctly and a connection to the Cloud Service has been established. {% content-ref url="/pages/-M2lp6Qa1mUWywvpIgfU" %} [Test case](/basic-invoice/installation-guide/test-case) {% endcontent-ref %} After the test case is done, the final step will be to create the the Job Queue Entries to activate the automation. {% content-ref url="/pages/-M2lp9lMm1z1Beob2CQ1" %} [Job Queue Entries](/basic-invoice/installation-guide/job-queue-entry) {% endcontent-ref %} There is also the possibility to use assisted setup for 'Golden EDI - Customer Setup' to batch update the customers with GEDI profiles. {% content-ref url="/pages/-M2mGsaxPWoNLfRrIYOM" %} [Batch update customers](/basic-invoice/installation-guide/batch-update-customers) {% endcontent-ref %} # Test case Run a test case to check that the connection to our cloud service has been established {% hint style="info" %} You can only run the test case when the connection is initially in test mode, once your connection is set to go-live, this test case will be sent out as a real e-invoice! {% endhint %} {% hint style="danger" %} **IMPORTANT** - To be able to run this test you need a Sales Invoice that we will later 'Post'. If your using a real invoice for the test, you'll also need to distribute it to the customer as normal! **The test will not be sent out as a e-invoice, it will only be sent to your e-mail.** {% endhint %} * In Business Central, search and go to the page "Sales Invoices" ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2mWf84IWuLkXZO8al8%2F-M2m_J30zqQOM5bV7GQv%2Fbild.png?alt=media\&token=122c26ec-7857-480b-aaad-15a1c35508e0) * Open the sales invoice that you want to run the test with. * Under the "Invoice Details" section, you will find the field 'GEDI Profile'. Change this to any of the 3 profiles, in order to activate the functionality. \ *(In the User Guide -* [*Customers* ](/basic-invoice/user-guide/customer-settings)*section we'll explain how to setup customers with this instead of each invoice).* ![Where to find the GEDI Profile on the Sales Invoice](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2m_a2jJTpwJ_aSzaTu%2F-M2ma3qk53xRXLiPuJT2%2Fbild.png?alt=media\&token=525a6c4f-8b30-438e-a71e-4e3ff98668e8) * When 'Posting' a invoice with the profiles activated, the app now controls that all key fields needed to send a basic invoice is filled in. If any such field is empty a error will tell you what is missing and abort the 'Posting'. ![Example error that might occur when trying to post a sales invoice](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2m_a2jJTpwJ_aSzaTu%2F-M2meNGuAuoKOXjAaQY1%2Fbild.png?alt=media\&token=1bea5d43-f320-4e5b-b147-020a29d637bf) {% hint style="info" %} Example of key fields required: * 'External Document No' (Table 36| Field 100) * 'Sell-to Contact' (Table 36| Field 84) {% endhint %} * When you go back to the invoice, and add the missing key fields, you can now try to 'Post' it again. * If you search and go to the page 'Posted Sales Invoice' you can find a column with 'GEDI Status' - this should now have status 'EDI Posting' ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2mrsFA37I2pbfhWChH%2F-M2my5nON7zoCgdnCGES%2Fbild.png?alt=media\&token=75fc3f59-0e71-4aaa-87cd-f31f9fa69be2) * Search and go to the page 'GEDI Message Queue'. * Here you will find a row with your invoice number in 'Message ID' column and with the 'Message Code' = 'SINV-86-PR', probably it's the last row in the list. * Mark the row, and go to 'Home' tab and click 'Run Message' to manually trigger the invoice.
* When it's done, you should have a new row in the list with the invoice number in 'Message ID' and 'Message Code' = 'SI-87-PE' and a 'GEDI Message ID'. * GEDI Message ID is the transaction id from the cloud service, if it succesfully responded.
* When you registered your organization in our portal, you picked a 'E-mail for EDI issues'. This e-mail address should now have received a e-mail with the EDI file attached. * If you go back to 'Posted Sales Invoices' you can see that the GEDI Status is now 'EDI Posted' ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2mrsFA37I2pbfhWChH%2F-M2myCCkrRI7wnFZDkXU%2Fbild.png?alt=media\&token=08f74ac9-a984-409d-afe1-476421dbc05b) {% hint style="success" %} If you received the e-mail this means the test was successful and the connection to the cloud service has been confirmed. {% endhint %} During this test you manually processed the message via our 'GEDI Message Queue', in the next step we will create and schedule 'Job Queue Entries' to handle this for us automatically in the background. # Job Queue Entries Schedule the messages to automatically process In this section we will create 2 different Job Queue Entries, 'GEDIQUEUE' & 'GEDIDELETE'. 1. **GEDIQUEUE**: will be set on a 5min schedule, each workday between 07:00 & 20:00, and will process all new messages to the Cloud Service 2. **GEDIDELETE**: will be set once a day schedule, at 04:00, and will clean up old GEDI data no longer needed. {% hint style="danger" %} If you have multiple Golden EDI solutions combined in your Business Central Company, and you already have Job Queue Entries configured, you don't need to create new identical once!\ e.g. if 'GEDIDELETE' already exist, don't create another one. {% endhint %} * In Business Central, search and go to the page 'Job Queue Entries' ### GEDIQUEUE - Job Queue Entry Card * Click new to create a new 'Job Queue Entry Card' ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2mrsFA37I2pbfhWChH%2F-M2n1UZnki_OC_Gkr7Mz%2Fbild.png?alt=media\&token=22095b25-7ece-4e49-a1fa-4bdc0d0d9950) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. * Fill in the 'Job Queue Entry Card' for 'GEDIQUEUE' as per screenshot or list bellow. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2ldF5Ogu5xZEyXimzB%2Fuploads%2FDST0lNcNLwwM8LBBWdq1%2Ffile.jpeg?alt=media) #### General Section: | Field | Value | | ----------------------- | ------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019001** | | Job Queue Category Code | **GEDIQUEUE** | #### Recurrence Section: | Field | Value | | --------------------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 0700 | | Ending Time | 2000 | | No. Of Minutes between Runs | 5 | * The 'GEDIQUEUE' 'Job Queue Entry' is now setup to processing the EDI messages automatically every 5min, each workday between 07:00 and 20:00 * Close the Pop-up and **don't restart the job queue yet.** ### GEDIDELETE - Job Queue Entry Car * Click new to create a new 'Job Queue Entry Card' ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2mrsFA37I2pbfhWChH%2F-M2n1UZnki_OC_Gkr7Mz%2Fbild.png?alt=media\&token=22095b25-7ece-4e49-a1fa-4bdc0d0d9950) * To the right of the 'General' Section, click 'Show more' to make sure you see all needed fields. * Fill in the 'Job Queue Entry Card' for 'GEDIDELETE' as Screenshot or list bellow. ![](https://firebasestorage.googleapis.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2ldF5Ogu5xZEyXimzB%2Fuploads%2FjyzTray2N1rVvKuAHtNP%2Ffile.jpeg?alt=media) #### General Section: | Field | Value | | ----------------------- | -------------- | | Object Type to Run | **Codeunit** | | Object ID to Run | **70019006** | | Job Queue Category Code | **GEDIDELETE** | #### Recurrence Section: | Field | Value | | ----------------- | ------- | | Run on Mondays | Checked | | Run on Tuesdays | Checked | | Run on Wednesdays | Checked | | Run on Thursdays | Checked | | Run on Fridays | Checked | | Starting Time | 0400 | * The 'GEDIDELETE' 'Job Queue Entry' is now now setup to clean up old GEDI data no longer used once a day at 04:00. * Close the Pop-up and **don't restart the job queue yet.** {% hint style="success" %} Golden EDI - Basic Invoice are now configured in your Business Central! {% endhint %} The next step will be to update the relevant customers with the 'GEDI Profile' and the correct e-invoice configurations. More on how to do this under **User Guide - Customers**. {% content-ref url="/pages/-M2lo\_Vx73e3ZeDbdxRu" %} [Customers](/basic-invoice/user-guide/customer-settings) {% endcontent-ref %} Once you have went thru the **User Guide - Customers** to understand how to correctly configure them for e-invoicing, you can also use our assisted setup for batch updating the relevant customers much faster. {% content-ref url="/pages/-M2mGsaxPWoNLfRrIYOM" %} [Batch update customers](/basic-invoice/installation-guide/batch-update-customers) {% endcontent-ref %} # Batch update customers After you have went thru the **User Guide - Customers** to understand how to correctly configure customer cards for e-invoicing, you can also use our assisted setup for batch updating the relevant customers much faster. {% content-ref url="/pages/-M2lo\_Vx73e3ZeDbdxRu" %} [Customers](/basic-invoice/user-guide/customer-settings) {% endcontent-ref %} * In Business Central, search and go to the page 'Assisted Setup'. * In 'Assisted Setup', click on 'Golden EDI - customer Setup' ![Search on "Golden EDI" to find it easier](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3C7ur9iEtpnSCuFzLX%2Fbild.png?alt=media\&token=b4c49c08-406d-4868-b803-eef9c6fc105a) * Select the Profile you want to add in the selection box above the list. * In the list of customers bellow, select the customer row that you want to add the profile to and click the button '**Set GEDI Profile'.** * You should now see profile you selected in the GEDI Profile column. * If you want to use **GLN** as identification reference, input the customer's GLN into the GLN column. * Repeat for every customer that you want to configure. * Click 'Done' when you are finished with all customers you wanted to change. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3CAmvYIdIFPc11ldCy%2Fbild.png?alt=media\&token=8f915838-751d-4262-ada7-a154ab2eb320) {% hint style="warning" %} Using this method to add the 'GEDI Profile' to the customer Card will not change the Document Exchange Type. This will still be empty as default, which means it's setup as E-invoice type. {% endhint %} {% hint style="info" %} 'Invoice Report' & 'Credit Report' columns, as well as the 'Document layout' button is not used for Basic Invoice. {% endhint %} # Go-live Before you go-live, you should have done these steps; * Configures business Central according to the guide * Made a test case to make sure you are connected to our cloud service * Signed the license agreement in Scrive that we sent you a link to earlier If all of above is done, and you are ready to go-live, login to our [portal](https://portal.goldenedi.com/) using the credentials we sent you earlier. \ Click the '**Ready to go Live'** button in the left panel. After this our support will follow up on your connection and turn off the **test mode**. Wait for our confirmation by e-mail that this is done. Once you have our go-live confirmation, go back to 'Job Queue Entries' in Business Central, and **restart** the '**GEDIQUEUE'** and '**GEDIDELETE'** job queues to start processing queued messages in our app. {% hint style="info" %} If you for some reason wants to stop or pause the automatic processing in the future, you should set 'Job Queue Entry' 'GEDIQUEUE' and 'GEDIDELETE' to 'Set On Hold'. You can restart it whenever you want to enable it again. {% endhint %} {% hint style="danger" %} The user that restarts the Job Queue Entry must have user permissation set 'SUPER' or 'GEDI ADMIN FULL'. {% endhint %} Follow up on your first invoices after this and make sure their GEDI status reaches 'EDI Posted', as described in the [invoice process.](/basic-invoice/user-guide/process) # Customers Configure the customers with Basic Invoice * In Business Central, search and go to the page 'Customers'. ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M2nHoe4S3ukWhVOwQal%2F-M2nOEu_G3dmB0vRrJva%2Fbild.png?alt=media\&token=72fb6348-12c6-4c5b-9810-032f7da81b7e) * Open up the customer card that you want to enable Basic Invoice for. * Under the 'Invoicing' section you will find the GEDI fields, click 'show more' to the right, to make sure you see all fields. **GEDI Profile;** should be set to either 'GEDI-BBAN', 'GEDI-BGIR' or 'GEDI-IBAN'. This will activate the customer to send out Basic Invoice, and will be inherited by all sales orders, invoice and credit notes created there after. {% hint style="info" %} The 3 profiles are setup to send different bank information that you want the payment of the invoice to be payed to, each customer needs to be setup with the correct payment type. The information is taken from "Company Information" page in BC. {% endhint %} | Description | GEDI Profile | Account from | Bank from | | -------------------------- | ------------ | ------------------------- | ------------------- | | Domestic Bank account | GEDI-BBAN | Bank Account No. (79\|14) | SWIFT Code (79\|39) | | Swedish BankGiro | GEDI-BGIR | Giro No. (79\|11) | Always: 'BGABSESS' | | International Bank account | GEDI-IBAN | IBAN (79\|38) | SWIFT Code (79\|3 | ![](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M5fXey5Sxp366L-X1gv%2F-M5fYGo7TOILO5DSxjXZ%2Fbild.png?alt=media\&token=0e32d252-8a27-4980-9d1e-bc9ec936f955) **GEDI Doc. Exchange Type;** here you can choose if the customer should receive invoice by other means than E-invoice. If it's empty and has the 'GEDI Profile', E-invoice is selected automatically. * **EDI** (or empty): Sent as e-invoice, only customers with connections to the network can receive e-invoices.\ ***Before you select EDI type, it is important to check with the customer that they are connected to the network!*** {% hint style="info" %} When sending a EDI type invoice it's important that the right identification reference is used to find the customer in the connected network. The most common Identification used is 'Domestic Organization No', but sometimes also 'GLN' and 'VAT Registration No' can be used. **It should be agreed with them what to use before sending your first e-invoice to them.** See table bellow for to fill this in on the customer card. {% endhint %} | Identification type | Customer Card Field | Table \| Field | | ------------------------ | --------------------- | -------------- | | Domestic Organization No | Registration No. | 18 \| 25 | | VAT Registration No | Vat Registration No | 18 \| 86 | | GLN / EAN | GLN | 18 \| 90 | | Other Identifications | GEDI Doc. Exchange ID | 18 \| 70019004 | {% hint style="info" %} Other Identifications can for example be; E-Address Finland and PEPPOL ID {% endhint %} * **PDF**: E-invoice will be converted to a PDF standard layout on network side and sent out as an e-mail to customer email address\ ***Before you select PDF type, it is important that the customer card has a email address under Address & Contact!*** {% hint style="warning" %} If e-mail invoices are common for you, we recommend you to use our [freemium PDF](https://docs.goldenedi.com/freemium/installation-guide/freemium) via your own SMTP instead. This will save you transaction fees from the network suppliers and your own PDF layout can be used. \ More information on Freemium on the [Appsource](https://appsource.microsoft.com/sv-se/product/dynamics-365-business-central/PUBID.golden_edi|AID.goldenedi|PAPPID.0c714171-3833-4378-90b5-3e9daac1dfc9?tab=Overview). {% endhint %} * **Paper**: E-invoice will be converted to a PDF standard layout on network side, printed to paper, and sent to the customer address via postal mail.\ ***Before you select Paper type, it is important to check that the customer is located in a supported country that the network sends to & keep in mind the postal fee will be added!***
If you have many customers to configure this way, we recommend you to use our batch update customers assisted setup. {% content-ref url="/pages/-M2mGsaxPWoNLfRrIYOM" %} [Batch update customers](/basic-invoice/installation-guide/batch-update-customers) {% endcontent-ref %} # Invoice Process Now when the customer cards are configured correctly, we look at how the invoice process to send e-invoices works with the Golden EDI app. When a sales order, invoice or credit note is created, it will inherit the 'GEDI profile' from the customer cards that we have configured. The GEDI profile will activate the basic invoice functions. {% hint style="warning" %} Before posting a sales invoice or credit note, it is possible to remove or change the 'GEDI profile' on it to override the customer cards for that specific sales invoice or credit note. {% endhint %} When you are trying to "post" a sales invoice or credit memo, the Golden EDI app will listen to this event and make a control on your sales invoice. If the 'GEDI profile' on the sales invoice or credit note is either 'GEDI-BBAN', 'GEDI-BGIR' or 'GEDI-IBAN', the control will then check if mandatory fields for the basic invoice are empty or not. If it finds a empty mandatory field, it will give you an error letting you know which field is missing. It will also stop the "posting" process for that sales invoice or credit note. | Mandatory Field | Description | Table \| Field | | -------------------- | -------------------------------------------------------- | -------------- | | External Document No | The buyer reference for this invoice, usually a order nr | 36 \| 100 | | Sell-to Contact | The buyer contact that should receive the invoice | 36 \| 84 | ![Mandatory Field for E-invoice](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M35wgf-3hv7W7pyC8aF%2F-M37-1yK4S_g2avKzfEk%2Fbild.png?alt=media\&token=54905c8b-02dd-4849-ae4d-2d154f595a16) If all mandatory fields contains values, the sales invoice will be posted. The posted sales invoice or credit note will then be added to the 'GEDI Message Queue' as an unprocessed message. {% hint style="info" %} At this point the '**GEDI Status'** for the posted sales invoice or credit note have been updated to '**EDI Posting'**, letting you know that the message is queued. {% endhint %} ![GEDI Status found on the Posted Sales Invoice](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3BkqLjUQtcJShVY0ej%2Fbild.png?alt=media\&token=5c9b9f7e-125a-47d6-b1d3-95e21d196982) Every 5 minutes during normal business hours, a 'Job Queue Entry' is scheduled to process all unprocessed message in the 'GEDI Message Queue', at this point they will be uploaded to the Cloud Service. {% hint style="success" %} If the upload to our cloud service was successful, the '**GEDI Status'** of the posted sales invoice or credit note will be updated to '**EDI Posted**'. {% endhint %} ![GEDI Status found on Posted Sales Invoices list](https://777361828-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M2ldF5Ogu5xZEyXimzB%2F-M3AweIjF1Bicd_3Xwxc%2F-M3C0CIZu3siqT7Ya2x5%2Fbild.png?alt=media\&token=15b9429c-64b5-4e17-a6eb-7807ae64646d) The Cloud Service will then translate your data to a standard e-invoice format and forward it to a VAN network for e-invoices. If any problems is found in the message, our cloud service or the VAN company who found the problem will contact you via e-mail with a error message. # Advanced Invoice Upgrade to advanced invoice to customize your e-invoice according to your business needs. If you have other requirements for your e-invoice that doesn't match our Basic Invoice standard template, it is possible to upgrade to an Advanced Invoice instead. In the Advanced Invoice our Application Specialist will customize the e-invoice according to your business needs. Here are some examples of added benefits of the Advanced Invoice: | Description | Basic Invoice | Advanced Invoice | | --------------------------------------------------- | -------------- | ---------------- | | Customize invoice data sent | No | Yes | | Attach your own PDF layout to e-invoice | No | Yes | | Invoice attachments can be included | No | Yes | | PDF layout & Attachment can be merged to 1 PDF | No | Yes | | Create multiple profiles for different requirements | No | Yes | | Status update & traceability | In Portal only | In App or Portal | | Cloud Service monitors Job Queue Entry Errors | No | Yes | | E-invoice to private person via bank | No | Yes | | Available on NAV and BC On-Prem versions | No | Yes |
# Standards ## Intro In this section you find some standard reference material related to the Golden EDI App. For example standard Units of measures, GEDI Codes etc that we refer to in other parts of the Implementation Academy. # GEDI Codes When creating new 'GEDI Message Codes' or 'GEDI Status Codes', it is recommended from Golden EDI side that you try to use a relevant code from the linked excel document. This is to avoid unecessary missunderstanding when communicating around these codes. Nevertheless, sometimes you need codes that is not yet defined in the standard and then you can name it whatever you like. If you choose to name your own codes, please try to follow the naming convention as descibed in the excel document. {% embed url="" %} The excel document has 3 tabs; 1. MessageCodes - A list of standard 'GEDI Message Codes'. 2. StatusCodes - A list of standard 'GEDI Status Codes'. 3. MessageCodeNaming - A description of naming convention for 'GEDI Message Codes' # GEDI Status Here you can find a list and description of the standard GEDI statuses. For more information on what a GEDI status is and how it works, please see the section in [Core Concepts / GEDI Status](/standard-app-core-concepts/concepts/gedi-status-codes)
#GEDI StatusDescription
1.EDI ImportedDocument is imported via GEDI.
2a.OK ControlDocument was controlled and no comments found.
2b.Error in ControlDocument was controlled an comments were found.
3.Requested (ACK)Acknowledge is triggered and in the GEDI message queue waiting processing.
4a.Sending (ACK)Acknowledge is processed and waiting to be uploaded to CIP.
4b.Error in ExportAcknowledge couldn't be processed. Usually a mapping error.
5a.Sent (ACK)Acknowledge was uploaded to CIP, processed, and sent to the next party.
5b.Error in Message (ACK)Acknowledge couldn't be uploaded to CIP. Usually a structure error in the message.
5c.Error from Cloud (ACK)Acknowledge couldn't be processed by CIP. Usually missing information or incorrect information.
6a.Received (ACK)Acknowledge was confirmed to be received by the next party.
6b.Error or Rejected (ACK)Acknowledge was rejected by the next party. Usually because their validation found an error.
7.Requested (CFM)Confirmation is triggered and in the GEDI message queue waiting processing.
8a.Sending (CFM)Confirmation is processed and waiting to be uploaded to CIP.
8b.Error in ExportConfirmation couldn't be processed. Usually a mapping error.
9a.Sent (CFM)Confirmation was uploaded to CIP, processed, and sent to the next party.
9b.Error in Message (CFM)Confirmation couldn't be uploaded to CIP. Usually a structure error in the message.
9c.Error from Cloud (CFM)Confirmation couldn't be processed by CIP. Usually missing information or incorrect information.
10a.Received (CFM)Confirmation was confirmed to be received by the next party.
10b.Error or Rejected (CFM)Confirmation was rejected by the next party. Usually because their validation found an error.
11.EDI RequestedMessage is triggered and in the GEDI message queue waiting processing.
12a.EDI SendingMessage is processed and waiting to be uploaded to CIP.
12b.Error in ExportMessage couldn't be processed. Usually a mapping error.
13a.EDI SentMessage was uploaded to CIP, processed, and sent to the next party.
13b.Error in MessageMessage couldn't be uploaded to CIP. Usually a structure error in the message.
13c.Error from CloudMessage couldn't be processed by CIP. Usually missing information or incorrect information.
14a.EDI ReceivedMessage was confirmed to be received by the next party.
14b.Error or RejectedMessage was rejected by the next party. Usually because their validation found an error.
15.PDF RequestedPDF is triggered and in the GEDI message queue waiting processing.
16.PDF SentPDF is sent via email.
17.PDF Requested (confirmation)PDF confirmation is triggered and in the GEDI message queue waiting processing.
18.PDF Sent (Confirmation)PDF confirmation is sent via email.
# Intermediate Documents Types
Document TypeDescriptionDirection
#EXTERNAL WAREHOUSE#
1Pick OrderOutgoing
2Pick ResultIncoming
3Purchase OrderOutgoing
4Purchase ResultIncoming
5Transfer OutboundOutgoing
6Transfer Out ResultIncoming
7Transfer InboundOutgoing
8Transfer In ResultIncoming
#PURCHASE FROM VENDOR#
10Purchase OrderOutgoing
11Purchase Order ConfirmationIncoming
12Purchase Despatch AdviceIncoming
13Purchase InvoiceIncoming
# Units of Measures Standard EDI Codes for Units of Measures Usually, most CIP Translators relies on standard EDI Units of measure codes that must be used from/to the app. These units of measure codes then needs to be converted in the Standard App to the units of measures defined in Business Central. This is done via a GEDI conversion documents that is usually called 'UNIT-STD'. As a general rule, a unit of measure used by EDI must be in singular. For example, if you would make a unit of measure like "10-PIECE" for 10 Pieces, then most likely it won't be able to transfer this correctly in the EDI. Sometimes you can get around this convertering it for example to "BUNDLE" or similar, but then you need to define your bundle in another way in the EDI, and many EDI receivers won't support this. Standard Unit codes used by the CIP: | EDI Codes | Description | | ----------- | ------------------------------------------------------------------------ | | **Piece** | Piece, the most common unit used. | | Undefined | Undefined, if exact match is not needed. | | Kilogram | Kilogram (KG) | | Litre | Litre (L) | | Milligram | Milligram (MG) | | Millilitre | Millilitre (ML) | | Millimetre | Millimetre (MM) | | Metre | Metre (M) | | SquareMetre | Square Metre (M^2) | | QubicMetre | Qubic Metre (M^3) | | MetricTon | Metric Ton | | Bundle | Bundle | | Box | Box / Number of Packs | | Gram | Gram (g) | | Centimetre | Centimetre (CM) | | Kilometre | Kilometre (KM) | | Day | Day | | Hour | Hour | | Month | Month | | Pallet | Pallet | | PalletEur6 | EUR 6 Pallet (800 X 600 mm). Also known as ISO 0 Pallet, 1/2 EUR Pallet. | | PalletEur | EUR Pallet (800 X 1200 mm). ISO 6780 ISO 1 Pallet. | | Bottle | Bottle, Non-Protected, Cylindrical | | Bucket | Bucket | | Pot | Pot | | Bag | XBG | | Roll | Roll | | Tray | Tray | | Pair | Pair | | Gigabyte | Gigabyte (GB) | | ServiceUnit | Service Unit | # Types ## General Types ### ArticleType
ValueCodeDescription
0Undefined
1Product
2Service
3Freight
### LineType
ValueCodeDescription
0Undefined
1Item
2Service
3Text
### ModeOfTransport
ValueCodeDescription
0Undefined
1Maritime
2Rail
3Road
4Air
5Mail
6Multimodal
7FixedTransportInstallations
8CourierService
### PartyIdType
ValueCodeDescription
0Undefined
1GLN
2OrgNumer
3MutuallyDefined
4Taxidentification
5Iso6523
6Duns
### PriceType
ValueCodeDescription
0Undefined
1Contract
2ContractDisc
3Current
4CurrentDisc
5Discount
6Additional
7List
8Information
9Net
## Order related Types ### OrderConfirmationLineStatus
ValueCodeDescription
0Undefined
1Added
2Changed
3NotAccepted
4Accepted
### OrderLineStatus
ValueCodeDescription
0Undefined
1Added
2Deleted
3Changed
4Unchanged
### OrderResponsStatus
ValueCodeDescription
0Undefined
1Received
2Rejected
3AcceptedWithoutChanges
4AcceptedWithChanges
### OrderType
ValueCodeDescription
0Undefined
1Original
2Change
3Replace
### TransferAcknowledgementCode
ValueCodeDescription
0Undefined
1Rejected
2Acknowledged
3InterchangeReceived
## DespachAdvice related Types ### PalletType
ValueCodeDescription
0Undefined
1SlipSheet
2Eur6Pallet
3EurPallet
4Eur2Pallet
5Pallet600x400
6Pallet400x300
7AustralianPallet
8Unspecified
9Pallet1000x600
10BlockPallet
11Dolly
12Eur3Pallet
13HorizontalDrumPallet
14IbcPallet
15Iso3Pallet
16Iso4Pallet
17T11Pallet
18Iso6Pallet
19Skid
20StringerPallet
21VerticalDrumPallet
22Pallet800x400
23Pallet610x1016
24Pallet610x508
25CustomPlatform
## Invoice related Types ### FinancialAccountType
ValueCodeDescription
0Undefined
1IBAN
2BBAN
3Domestic(E.g. BankGiro)
### InvoiceAllowanceOrChargeType
ValueCodeDescription
0Undefined
1FreightCharge
2ServiceCharge
3PackingCharge
4InvoiceDiscount
5ReductionForPickupOfGoods
6SmallOrderFee
7Other
8EnvironmentCharge
9GenericCharge
10GenericAllowance
11PackageCharge
### InvoiceType
ValueCodeDescription
0Undefined
1CommercialInvoice
2CreditNote
3DebitNote
4SummaryDebitNote
5SummaryCreditNote
6CreditNoteAppendix
### JustificationForTaxExemptionCode
ValueCodeDescription
0Undefined
1ReturnableAsset
2SupplyOfPharmaceuticals
3EuExport
4ReverseVat
### TaxCategory
ValueCodeDescription
0Undefined
1ExcludedFromVAT
2Food
3RestaurantServices
4Standard
5PapersBooksEtc
6ZeroTax
7VatReverseCharge
8VatExemptEEAIntraCommunity
### TaxType
ValueCodeDescription
0Undefined
1Vat
2EnvEnvironmental tax
# Welcome Guides and useful information for partners implementing and managing integrations built on Golden EDI. We designed this comprehensive guide to help you unlock the full potential of Golden EDI. Whether you aim to provide support for existing client integrations, extend our product for custom solutions, or implement entirely new integrations, you'll find the insights you need right here. So, grab a cup of something nice ☕, sit back, and let's dive in! # Create Messages Learn how to create messages in Golden EDI to export, validate or trigger actions. *By following this guide, you'll be able to make the most out of the `CheckMessageToCreate` function in Golden EDI. Have questions? Feel free to reach out!* ### Introduction The `CheckMessageToCreate` function is an essential part of Golden EDI's message queue architecture. This guide aims to provide a comprehensive understanding of how to utilize this function for various purposes, such as exporting to our Cloud Integration Platform, triggering actions, and more. ### GEDI Message Queue Messages in the GEDI Message Queue serve multiple roles—importing, exporting, validation, and action triggering. Creating a queue line with the correct parameters allows Golden EDI to process the message as per the configuration settings. The processing can be an internal only process or generate data to be read by our Cloud Integration Platform to interface with external systems, processes or clients. ### Function Signature To create a message in the queue we have a public function called `CheckMessageToCreate` in the `GEDI Management` Codeunit. This method has the following signature: {% code title="GEDI Management" fullWidth="true" %} ```al procedure CheckMessageToCreate(GEDIProfileCode: Code[10]; MessageID: Code[50]; MessageDocumentNo: Code[50]; MessageSelection: Integer; ManualImmediateRun: Boolean): Boolean; ``` {% endcode %} **Parameters:** * `GEDIProfileCode`: The profile with which the message should be created. * `MessageID`: The ID of the message, often the document number for the record. * `MessageDocumentNo`: An additional document number. * `MessageSelection`: Indicates what kind of message to create. * `ManualImmediateRun`: Flag to indicate if immediate processing is required. **Return Value:** * Returns `true` if a message was created; `false` otherwise. #### Concepts * **Profile and Selection**: The combination of `GEDIProfileCode` and `MessageSelection` dictates whether a message should be created and its properties. * **Multiple Queue Lines**: A single call to this function can result in multiple lines in the queue based on the configuration. * **MessageID:** Usable from inside a mapping during processing of the message, allowing you to easily open the correct record. * **MessageDocumentNo**: Often the same as the `MessageID`, has no use except to make it possible to locate messages in the queue by an additional identifier. * **Message Selection Hooks**: Built-in selections like "Manual Hook 1" to "Manual Hook 10" are useful for adding listeners for new events. Other selections exist that can also be used. {% hint style="warning" %} Avoid using the same message selection for different events and triggers. While the message setup for each profile can make it possible to trigger different codes it is still not recommended since it can make the configuration difficult to understand and maintain. {% endhint %} ### Examples Here you can find a collection of examples on how to utilize this function to create messages. #### Export Warehouse Document This is an example for how you would call the method for a Record pointing to an `Warehouse Activity Header`. The setup below uses the selection called `Manual Hook 1` but you may choose another one depending your use case and system. The profile does not exist on the record so we use a fixed profile. You could use a conversion document or any other method of your choosing to dynamically select the profile as well. {% code fullWidth="true" %} ```al procedure SendWhseDocument(var Rec: Record "Warehouse Activity Header") var GEDIManagement: Codeunit "GEDI Management"; GEDIMessageSelection: Record "GEDI Message Selection"; begin // Profile might exist on the document or you can set a fixed value SendingProfile := 'ONGOING'; // We use the fixed profile and the "Manual Hook 1" selection to find the codes to create. GEDIManagement.CheckMessageToCreate(SendingProfile, Rec."No.", Rec."No.", GEDIMessageSelection.Usage::"Manual Hook 1", false); end; ``` {% endcode %} ### Process Immediately This code example shows how you would use the `RunMessageQueue`method on `GEDI Queue Handler` in combination with `CheckMessageToCreate` to both create and process messages immediately. As you can see we call the `RunMessageQueue` with the same information used in the call to create one or more messages. The information we pass to the method is used to filter down the message queue to the specific lines we should process. {% code fullWidth="true" %} ```al procedure CreateAndRunImmediately(var Rec: Record "Sales Invoice Header") var GEDIManagement: Codeunit "GEDI Management"; GEDIQueueHandler: Codeunit "GEDI Queue Handler"; GEDIMessageSelection: Record "GEDI Message Selection"; GEDIMessageQueue: Record "GEDI Message Queue"; begin // Try to create message(s) for the invoice that are configured to be processed immediately. if GEDIManagement.CheckMessageToCreate(Rec."GEDI Profile", Rec."No.", Rec."Order No.", GEDIMessageSelection.Usage::"Manual Hook 1", true) then begin // Since we did manage to create something, we can call the method "RunMessageQueue" on "GEDI Queue Handler" to actually process them immediately GEDIQueueHandler.RunMessageQueue(GEDIMessageSelection.Usage::"Manual Hook 1", Rec."GEDI Profile", Rec."No.", '', 0, false, '', false, GEDIMessageQueue); end; end; ``` {% endcode %} # Modify Email Messages Learn how to modify e-mail being sent through our free PDF automatization *By following this guide, you'll be able to make the most out of the `OnBeforeSendEmailMessage` in Golden EDI. Have questions? Feel free to reach out!* ### Introduction The `OnBeforeSendEmailMessage` event has been added to our free PDF atomization functionality in order to allow you to modify e-mails through code right before they are sent over to the standard BC functionality. This event keeps and passes the reference to the source document as a record reference allowing you to lookup any information you need to do the appropriate changes. ### Event Signature In order for you to be able to do the changes you need to the outgoing e-mail we've made sure to add as much information we can to the event. The event has the following signature: {% code title="GEDI PDF Function" fullWidth="true" %} ```al procedure OnBeforeSendEmailMessage(var Email: Record "Email Item"; var SelectedScenario: Enum "Email Scenario"; var SourceRef: RecordRef; DocumentNo: Code[50]; var IsHandled: Boolean) ``` {% endcode %} **Parameters:** * `Email`: The email item we've created, which will be passed to the standard e-mail handler after the event subscribers are done and `IsHandled` is set to `false`. * `SelectedScenario`: The e-mail scenario that has been used. * `SourceRef`: A record reference pointing to the source document that has been used to generate the e-mail and the attached PDF document. * `DocumentNo`: The document no. for the source document pointed to by the record reference. * `IsHandled`: Flag to indicate that you've manually handled the e-email and we should not continue to process this e-mail. If set to `true` it will not be passed by us to the standard E-mail functionality. {% hint style="warning" %} Do not set IsHandled to true unless you manually call the `Send` method on the `Email Item`. Likewise, do not forget to set this to true if you **DO** send the item yourself. Otherwise the recipient will end up with multiple e-mails. {% endhint %} ### Examples Here you can find a collection of examples on how to utilize this function to modify outgoing e-mails. #### Change the E-mail Subject This is an example for how you would build a listener that changes the subject of the e-mail item before being sent to the recipient. This example verifies that the source document is an invoice and then uses the `Sell-to Customer No.` to build a new subject with the customer name and the invoice number. {% code fullWidth="true" %} ```al [EventSubscriber(ObjectType::Codeunit, Codeunit::"GEDI PDF Function", 'OnBeforeSendEmailMessage', '', true, true)] local procedure OnBeforeSendEmailMessage(var Email: Record "Email Item"; var SelectedScenario: Enum "Email Scenario"; var SourceRef: RecordRef; DocumentNo: Code[50]; var IsHandled: Boolean) var FldRef: FieldRef; CustomerNo: Code[20]; Customer: Record Customer; begin // Verify that the source is a Sales Invoice Header, since we only want to modify invoice E-mails. if SourceRef.Number() = Database::"Sales Invoice Header" then begin // Get the Sell-to Customer field. FldRef := SourceRef.Field(2); CustomerNo := FldRef.Value(); // Get the customer record for the Sell-to Customer. Customer.Get(CustomerNo); // Update the subject for the E-mail. Email.Subject := StrSubstNo('Hello, %1, here is your invoice %2.', Customer.Name, DocumentNo); end; end; ``` {% endcode %} #### Change the E-mail Recipient and/or Sender This example shows you how you can modify either the sender or the recipient e-mail address. For this example we've set a requirement that the document must be an order and then pick the recipient from field "Sell-to E-mail" on the order itself as the recipient if its filled in, leaving it as-is should the field be empty. We also show how to change the "From Address" in the rare cases where you might want to dynamically change this based on some information. For illustrative purposes we only use the e-mail set in "Company Information". {% hint style="danger" %} Changing the "From Address" requires that the E-mail Account configured in the E-mail Scenario has explicit **Send As** or **Send on Behalf Of** permission for that address - this must be configured in your mail provider (e.g. Exchange/Microsoft 365, SMTP relay). Without these permissions, e-mails will **fail to deliver**. Many providers reject such e-mails **silently and without a bounce notification**, meaning you will receive no error in Business Central and may not discover the problem until much later. {% endhint %} {% code fullWidth="true" %} ``` [EventSubscriber(ObjectType::Codeunit, Codeunit::"GEDI PDF Function", 'OnBeforeSendEmailMessage', '', true, true)] local procedure OnBeforeSendEmailMessage(var Email: Record "Email Item"; var SelectedScenario: Enum "Email Scenario"; var SourceRef: RecordRef; DocumentNo: Code[50]; var IsHandled: Boolean) var FldRef: FieldRef; SellToEmailAddress: Code[80]; CompanyInformation: Record "Company Information"; begin // Verify that the source is a Sales Header, since we only want to modify order E-mails. if SourceRef.Number() = Database::"Sales Header" then begin // Get the Sell-to E-Mail field. FldRef := SourceRef.Field(172); SellToEmailAddress := FldRef.Value(); // If the e-mail is set then we switch to this as the recipient of the order confirmation e-mail. if SellToEmailAddress <> '' then begin Email.Validate("Send to", SellToEmailAddress); end; // Get the main company e-mail address from the Company Information table and set it as the sender of the e-mail. if CompanyInformation.Get() then begin Email.Validate("From Address", CompanyInformation."E-mail"); Email.Validate("From Name", CompanyInformation."Name"); end; end; end; ``` {% endcode %} #### Change the Primary E-mail Attachment Name This example demonstrates how to rename an email attachment. It verifies that the email contains at least one attachment and that the source document is an invoice. The example then uses customer information from the `Sell-to Customer No.` to create a personalized name for the primary PDF attachment. This technique takes advantage of the fact that attachments are always stored in the same order they are added. Since we always generate and attach the primary document first, it will always be at index 1. Then you will find the incoming documents attached to the invoice (if any) in the same order they are stored in the system, from index 2 and above. {% code fullWidth="true" %} ```al [EventSubscriber(ObjectType::Codeunit, Codeunit::"GEDI PDF Function", 'OnBeforeSendEmailMessage', '', true, true)] local procedure OnBeforeSendEmailMessage(var Email: Record "Email Item"; var SelectedScenario: Enum "Email Scenario"; var SourceRef: RecordRef; DocumentNo: Code[50]; var IsHandled: Boolean) var FldRef: FieldRef; CustomerNo: Code[20]; Customer: Record Customer; TempBlobList: Codeunit "Temp Blob List"; FileNames: List of [Text]; Name: Text; begin // Check that the email contains attachments and the source is an invoice if Email.HasAttachments() and (SourceRef.Number() = Database::"Sales Invoice Header") then begin // Get the Sell-to Customer field. FldRef := SourceRef.Field(2); CustomerNo := FldRef.Value(); // Get the customer record for the Sell-to Customer. Customer.Get(CustomerNo); // Get the list of all attachments (in attached order, i.e. first is always invoice/credit/report and the rest are "incoming document" attachments) Email.GetAttachments(TempBlobList, FileNames); // Update the name for the generated report file Name := StrSubstNo('Invoice %1 - %2 - %3.pdf', DocumentNo, Customer.Name, Customer.Contact); FileNames.Set(1, Name); // Replace the attachments with the updated name Email.SetAttachments(TempBlobList, FileNames); end; end; ``` {% endcode %} #### Add a new Attachment to the E-mail This example explains how to generate a new PDF and attach it to the email. It filters similarly to other examples and generates a sales report for all customers, attaching it to the email with a name specific to the customer. This method allows adding special reports or attachments without altering the standard PDF generation by Golden EDI. {% code fullWidth="true" %} ```al [EventSubscriber(ObjectType::Codeunit, Codeunit::"GEDI PDF Function", 'OnBeforeSendEmailMessage', '', true, true)] local procedure OnBeforeSendEmailMessage(var Email: Record "Email Item"; var SelectedScenario: Enum "Email Scenario"; var SourceRef: RecordRef; DocumentNo: Code[50]; var IsHandled: Boolean) var FldRef: FieldRef; CustomerRef: RecordRef; CustomerNo: Code[20]; Customer: Record Customer; GeneratedReport: OutStream; TempBlobList: Codeunit "Temp Blob List"; TempBlob: Codeunit "Temp Blob"; FileNames: List of [Text]; Name: Text; begin // Check that the email contains attachments and the source is an invoice if Email.HasAttachments() and (SourceRef.Number() = Database::"Sales Invoice Header") then begin // Get the Sell-to Customer field. FldRef := SourceRef.Field(2); CustomerNo := FldRef.Value(); // Get the customer record for the Sell-to Customer. Customer.Get(CustomerNo); // Open the customer as a RecordRef CustomerRef.GetTable(Customer); // Get the list of all attachments Email.GetAttachments(TempBlobList, FileNames); // Use the TempBlob to initialize the OutStream TempBlob.CreateOutStream(GeneratedReport); // Generate a sales report for the customer (this will generate a summary of all customers) Report.SaveAs(Report::"Customer - Sales List", '', ReportFormat::Pdf, GeneratedReport, CustomerRef); // Add the TempBlob to the list TempBlobList.Add(TempBlob); // Create a nice name for the attachment Name := StrSubstNo('%1 - Sales List.pdf', Customer.Name); // Add the name to the list so we link the name to the attachment FileNames.Add(Name); // Update the stored attachments Email.SetAttachments(TempBlobList, FileNames); end; end; ``` {% endcode %} # Entra Application Security How our Entra (Azure AD) application integrates with Microsoft 365 for Business Central. Details scope, security measures and compliance. ## Introduction This page details how we access business central from our Cloud Integration Platform and which security measures exists to make sure that your Business Central environment stays safe. ### Summary * Our Entra (Azure AD) Application has been scoped to only ask for access to be able to sign-in and access Business Central. It does **not** ask request, nor is it granted, permissions to other Microsoft 365 services (e.g. Exchange, SharePoint, Teams). * All calls to Business Central are mode over secure (HTTPS) connections and is authenticated with OAuth, with a short-lived token that is refreshed often. The client secret used to generate the access token is also limited in lifespan to avoid having any long lived keys. * All access keys are stored securely in vaults and can only be accessed by our Cloud Integration Platform. **No other system** is allowed access to this vault. * Our Cloud Integration Platform must also have a configured connection to actual access any Business Central environment. Without this no requests to the environment will be made. * Possibility to scope the permissions further in Business Central to allow access only to certain companies and tables. By default it's limited to a limited set of Golden EDI tables, only what is required by the intergration. * We follow Microsoft best practices and utilize their standard identity and consent frameworks for the communication. This ensures adherence to security policies and standards. ## Entra (Azure AD) Application Scope *Client ID:* [*56207283-61ab-4134-978e-54bccce5c559*](#user-content-fn-1)[^1] We have explicitly limited the Entra Application (named Golden EDI) to a limited set of API permissions that scopes it to only allow sign-ins and access to Business Central. They are the minimum required set of permissions to allow services to access Business Central APIs. The Graph API we request is used for delegated login towards Business Central and it's what allows us to login as an unlicensed user. This user is configured inside Business Central on the Entra Application card and can be scoped to tables and companies as desired by using standard permissions. **Permissions** * Microsoft Graph - [User.Read](https://graph.microsoft.com/User.Read) - Delegated\ *Allows you to sign in to the app with your organizational account and let the app read your profile. It also allows the app to read basic company information. It further allows access to your Business Central as user Golden EDI.* * Dynamics 365 Business Central - [API.ReadWrite.All](https://dynamics.microsoft.com/business-central/overview/API.ReadWrite.All) - Application\ *Grants full access to the Business Central web services APIs. These APIs provide the capability to call web services APIs and modify Business Central data.* **Consent** During the grant consent procedure you will be shown dialog that shows which permissions that we ask for and it will (**and should**) show a blue seal next to our organisation name showing that we are identified publishers.

The consent dialog also shows the requested permissions for validation

## Entra Application Consent Before our Entra Application is allowed to access any Business Central environment a user must grant consent. This is a manual action taken by someone with Entra administrator permissions in the Entra tenant that contains the Business Central environment. {% hint style="info" %} **Entra Tenant** - A secure, dedicated instance of Microsoft's identity and access management service. It defines the boundaries for the organisation and contains and manages identities, services and permissions. **Business Central Environment** - An instance of Business Central that is isolated with its own database, companies, settings, users, and customizations. There can be one or more environments within one Entra Tenant. {% endhint %} {% hint style="warning" %} If consent is not given or if it has been revoked no further access to Business Central will be possible until the procedure is redone. {% endhint %} This action is initiated from within the Business Central environment that one wants to allow Golden EDI to access. It can be started from the "Entra Applications" page or by running the assisted setup "Golden EDI - Initialize", which must be called to register the application. {% hint style="info" %} User must have SUPER and SECURITY in Business Central and must be an administrator within the Entra tenant. {% endhint %} Within the "Microsoft Entra Applications" list our app should be present, if not, it can be added by using the assisted setup or manually by clicking new and entering all relevant details. During registration of the application the system will automatically create a user with the same name. This is the user used by our Cloud Service and it can be scoped as normal in Business Central using permissions.

The page "Microsoft Entra Applications" lists all added applications.

Clicking on the listed application show a card page showing all the relevant details and permissions for the Entra Application. Here you can also initiate the "Grant Consent" procedure if it wasn't done during the initialization.

The card shows the details for the registered application and allows consent to be granted by clicking "Grant Consent".

When this action is initiated the user will be presented with a dialog that they will have to accept, assuming they have adequate permissions within both Business Central and Entra. **Any permissions not listed in the dialog will not be granted**.

The dialog presented during the consent procedure, only by clicking "Accept" will access be granted.

## Entra Application User and Permissions When the Entra Application is created a user will be automatically created in Business Central. This user is what the Cloud Integration Platform will use for identification purposes when making calls to the Business Central environment. This user will by default, if added through our assisted setup, have a purpose made permission set that builds upon the standard "D365 BASIC" and "D365 AUTOMATION" permission set, with a few of our tables and pages included. This permission set is named "GEDI CLOUD PLATFORM" and can be added to the user if it isn't already added. {% hint style="info" %} When other ISV applications are installed into the same Business Central environment further permissions might be necessary. This is due to the way most application does license checks which requires our user to have, at minimum, read access to the license tables in the respective application. {% endhint %} The permissions can be found on the Entra Application card for the application. it is possible to scope the permission to limit the rights to one or more specific companies in the environment. We do not do this by default, instead opting to set the limited permissions without company scoping. {% hint style="info" %} The permissions can only be adjusted by a SUPER user with SECURITY permissions. {% endhint %}

The permissions can be found below the general part on the application card.

Below is a list of all the permissions included in the limited permission set "GEDI CLOUD PLATFORM" that we use and recommend for our application user. **Included Rights** * Inherited rights from "*D365 BASIC*" * Allows login from APIs through OAuth, without this we can't access the system. * Table "*GEDI Message Queue*" and pages "*GEDI Message Queue*", "*GEDI API Message Queue*" * Used to be able to read and write messages to the message queue. * Table "*GEDI Message Line*" and pages "*GEDI Message Lines*", "*GEDI API Message Lines*" * Used to be able to read and write message contents for a message in the queue. * Table "*GEDI Class Information*" and page "*GEDI Class Information*" * Used to able to update the classes and their properties that are available to be used when creating mappings. * Table "*GEDI Profile*" and page "*GEDI Profiles*" * Used to read the profiles configured in the system and their connection details. This determines what Cloud Integration Platform connections are available. * Table "*GEDI Message Code*" and page "*GEDI Message Codes*" * Used to read the configured message codes and find codes that the Cloud Integration Platform should be able to read from the message queue. * Table "*GEDI Class Setup*" and page "*GEDI Class Setup*" * Used to find which message code, class and property should be used when writing a message to the queue. * Table "*GEDI Setup*" * Used to read setup information during handling. * Page "*GEDI Library List*" * Deprecated page used to interact with available libraries in the app, has been replaced. * Page "*GEDI API Message Lines DI*" and page "*GEDI API Message Lines DI Part*" * Used to do deep insert writes to the system, an option to write a message to the queue and bulk write the lines for the message. The Cloud Integration Platform uses this when writing messages in the newer versions of the application instead of "GEDI API Message Queue" and "*GEDI API Message Lines*". ## Cloud Integration Platform Security During the normal operations of the Cloud Integration Platform it will need to login and make calls towards Business Central frequently. To ensure both adequate performance and security we've made sure to optimize the storage of the tokens used for authentication. The longer lived security key and tokens, used to generate the ephemeral access token, is stored securely in a key vault. This vault is limited to only grant access to the Cloud Integration Platform, and **no other system has access**. The shorter lived access token is stored in a state database. The standard lifetime for these, as enforced by Microsoft, is twenty minutes. When these have expired we request a new token using the security details. [^1]: This is the identifier for our Entra Application # Transaction Tables List of tables that hold transaction data for Golden EDI ### **Golden EDI Base Application** These table hold the transaction data during standard operations. Before going live with a system, ensure that these tables a cleared to avoid any issues. {% hint style="danger" %} Manual clearing in a live system is discouraged; use the GEDIDELETE job queue for routine cleanups to prevent issues like duplicate imports or incorrect statuses. {% endhint %}
Table No.Table NameDescription
70019001GEDI Message LineContents of a message in the queue.
70019002GEDI Message QueueQueue for all incoming and outgoing messages.
70019011GEDI Message LogLog of processed messages, used by the duplication check.
70019020GEDI Status Ledger EntryHolds all document statuses as created by Golden EDI.
70019021GEDI Ship Advice HeaderThe header for a shipment advice.
70019022GEDI Ship Advice Log Unit LineLogistic units connected to a shipment advice.
70019023GEDI Ship Advice Unit LineItems on a logistic units.
70019033GEDI Data Set ValuesTemporary stored for query values.
### **Golden EDI Extended Platform** It's advisable to clear them during testing phases or before system launch, while manual clearing during regular operations should be avoided. Single document deletions are permissible via the GUI, as configurations can be set to restrict deletions based on document statuses, thereby ensuring safe deletion practices. {% hint style="info" %} For automated clearing configurations, contact our support team. {% endhint %}
Table No.Table NameDescription
70845581GEDI Intermediate HeaderRepresents the header of an intermediate document.
70845582GEDI Intermediate LineContains lines associated with a single header.
# Releases Release notes for Golden EDI This page describes changes in the public releases of Golden EDI. We aim to keep this up-to-date with every release made to AppSource. Private releases or releases made to OnPrem environments do not necessarily reflect what is described here but in most cases it is the sames features and changes. #### New Versioning Scheme: AL-Go Standard (Effective from Version 23.0.5.0) Starting from version 23.0.5.0, we've adopted the AL-Go standard for our versioning scheme. This new standard means that the version number you see will solely refer to our Golden EDI version and will no longer indicate the compatible Business Central version. In the AL-Go system, the first two numbers represent major and minor changes, while the last two are for automatic revisions. **Old Versioning Scheme (Before 23.0.5.0)** Before transitioning to the AL-Go standard, our versioning had a different methodology. In this old scheme, we only referred to the "Golden EDI version," which consisted of the three last numbers in the version number as visible in the application. {% hint style="info" %} For example, an app with version 20.4.7.5 meant it was version 4.0.0 validated against Business Central 20 and forward. The Business Central version in the version number was considered the minimal supported version. Older versions of Business Central might have been compatible, but they were not tested. {% endhint %} ### Numbering The numbering of our versions aims for clarity. The first two numbers indicate major and minor changes respectively, while the last two numbers are for automatic revisions based on various factors such as bug fixes and small adjustments. * **Major Changes**: These are changes that may not necessarily alter how you interact with Golden EDI on a daily basis but can include significant internal upgrades. Such upgrades are aimed at improving system performance, ensuring long-term compatibility, and other foundational improvements that better the overall quality and stability of the product. * **Minor Changes**: These are more targeted improvements that enhance functionality without significantly altering your daily operations with Golden EDI. ### Backwards Compatibility We are committed to ensuring that our releases, both big and small, remain backward compatible with older setups and configurations. So go ahead, make that version leap; your configurations should function just as smoothly as before! # 28.5 Changelog for Golden EDI version 28.5 that was released on 2026-05-23 ## Description Welcome to our latest release! Highlights of this release are * Support for automated backups of GEDI configuration. * Frequently used *Codeunits\**, used in Warehouse Integration, IC and advanced trade processes utilizing Golden EDI extended platform. \*A *Codeunit* is a "program object" typically consisting of advanced "Business logic". The Golden EDI mapping / message engine allows the user to assign *Codeunits* for execution, thus making it possible to utilize these advanced objects by GEDI Mapping Documents. ### Why we made these changes **Automated GEDI backups** The major part of the Business logic in a Golden EDI implementation is defined by "Mapping Documents" and various Golden EDI setups. Therefore its crucial to keep track of the setup, both to be able to see what has been changed, but also to keep an extra backup copy of the setup just in case. In this release, a backup will be automatically generated whenever a change in setup is identified (all changes done within 24 hours will be stored in same backup). The backups are downloaded and stored in Golden EDI Cloud Platform automatically. For future releases this will enable advanced features like (many of them likely AI processed): * Automatically highlight changes done in configuration. * Automatically identify issues with setups. (For example obsoleted fields etc.) * Automatically generate documentation. **Advanced *****Codeunit***** "Toolbox"** Some advanced features in Warehouse Integrations, Inter Company and advanced trade have required installation of additional *Codeunits*. In this release we have identified frequently used features / business logic, generalized them a bit and included them in the app so they can be used in "Golden EDI Mapping Documents" without having to install a PTE. ### What this means for you **For Most Users**: No Action Required * Backups of the entire GEDI Setup are now created automatically. * No longer required to request and install a PTE for some advanced frequently used mapping logic. ### For Partners and Integrations **If you have custom integrations using the Golden EDI API:** * The API contract version has been updated to version 3.2. ### **Changelog** **Golden EDI** * Automated Backups. New page can be opened to view backups from the "GEDI Setup". * Added a new *line type* in "Gedi Mapping", "Run Event". This type extends the customizability possibilities in mappings by providing more context to the "listener". **Extended Platform** * Codeunit "Toolbox" for advanced Inter Company, Warehouse and Trade features utilizing Extended Platform. # Changes The planned future changes to Golden EDI. Currently we have nothing public to divulge on future planned changes. There are things to come but nothing we can talk about right now. # 27.4 Changelog for Golden EDI version 27.4 that was released on 2026-02-04 ## Description Welcome to our latest release! This is a small but crucial release where we've introduced important improvements to how Golden EDI stores message data, along with enhancements to the communication between Business Central and our Cloud Platform. These changes are designed to ensure long-term reliability and better performance for all customers. ### Why we made these changes **Message Line Storage (V2)** Over time, as customers send and receive large volumes of EDI messages, the underlying database table that stores the message contents can accumulate a large number of records. The current table that stores this information had some technical limitations that could cause performance issues and technical limitations when the volume got large. To address this, we've introduced a new table for this data that removes this entirely. This will ensure that Golden EDI can continue to handle your flows and EDI for years to come, regardless on how many messages you process. **Cloud Platform Integration** We've also updated how the communication works between your Business Central and our Cloud Platform. We've co-located some of the information into one API to reduce the number of calls we need to make to your system. Resulting in improved performance and lower load on our systems. ### What this means for you **For Most Users**: No Action Required * All new messages created after the updated will automatically use the improved table. * Your existing workflows, mappings, and configurations remain unchanged. * You should not notice any difference in how you use Golden EDI. **For Existing Messages** Messages created before this updated will continue to work as before. If needed, administrators can upgrade individual messages to the new table. This is optional and only necessary in specific support scenarios. ### For Partners and Integrations **If you have custom integrations using the Golden EDI API:** * The API contract version has been updated to version 3.0 * New API endpoints (v2.0) are available for the updated message line structure * The Message Queue API now includes Direction and Connection ID fields directly, reducing the need for additional API calls * Existing v1.0 API integrations continue to function normally We recommend reviewing your integrations and updating to the v2.0 API endpoints when convenient to benefit from the improved structure ### **Changelog** **Golden EDI** * Introduce Message Lines V2 table to replace the previous message line storage. * Added Direction and Connection ID fields to the message queue for improved API usage. * Updated API contract to version 3.0. * Added v2.0 API endpoints for messages lines and message queue to utilize the new tables and fields. # 27.0 Changelog for Golden EDI version 27.0 that was released on 2025-09-22 ## Description Welcome to our latest release! This is a small release providing compatibility with Business Central 27 and some improvements to compatibility with other ISVs. ### **Changelog** **Golden EDI** * Validated compatibility with Business Central 27. * Added function to disable currency exchange rate update in imports. * Improved compatibility with SweBase in PDF functionality. **Golden EDI - Extended Platform** * Validated compatibility with Business Central 27. * Added approval fields to Intermediate Line table for AP Automation. # 26.1 Changelog for Golden EDI version 26.1 that was released on 2025-08-08 ## Description Welcome to our latest release! This update a small but noticeable performance improvement to the Extended Platform workspaces and documents. ## Changelog * Optimized document retrieval and filtering operations for faster response times in Extended Platform. * Improved decimal field aggregations in Extended Platform. # 26.0 Changelog for Golden EDI version 26.0 that was released on 2025-06-04 ## Description Welcome to release 26.0! This update brings several improvements to enhance system performance, reliability, usability, and expanded integration features. Highlights includes reliability improvements, new event handlers, enhanced email processing with better integration to SweBase, and a new feature called Configuration Options to allow simplified end-user setup management in future setups. We've also upgraded our Extended Platform to what we call V2, providing greater flexibility while maintaining existing configuration approach. ## Changelog **Golden EDI** **Enhanced Reliability** * Improved email generation with corrected subject line handling for SweBase integration * Enhanced PDF mailing workflows with proper source document association * Streamlined comment line processing with automatic splitting for lengthy content **Advanced Workflow Features** * New pre-posting control events for sales shipments with customizable triggers * Enhanced mapping protection requiring closed status before deletion * Expanded Message ID support allowing full 50-character length in workflows * Improved drop shipment receipt processing with automated message selection **Expanded Integration Capabilities** * New invoice discount calculation fields for both sales and purchase documents * Enhanced import/export mapping functions with advanced filtering options * Added "Company Name" function for dynamic company display integration * Support for third field filtering in export mapping operations **User Experience Enhancements** * Introduction of Configuration Options for simplified end-user setup management * Added GEDI document exchange fields to vendor management * Enhanced control document navigation with multi-level table references * Optional color/style settings for GEDI Status fields to optimize performance * Improved visibility of GEDI fields and statuses on posted purchase documents **Extended Platform - Major Upgrade** **Platform Evolution** * Upgraded to Extended Platform v2 with support for replaceable pages and tables * Maintained compatibility with existing configuration methods during transition **Access Control & Performance** * New GEDI Viewer Groups for granular workspace access management * Optimized quantity calculations across all posting operations (Sales, Purchase, Receipt, Shipment) # 24.4 Changelog for Golden EDI version 24.4 that was released on 2024-10-03 ## Description Welcome to our latest release! This update brings several improvements to enhance system performance, reliability, and usability. The primary changes this release is the migration to "user-defined layouts" for custom report layouts and e-mail body layout with a fallback to the old fields. In addition we also switched to use the standard Business Central functions to generate the e-mail subject and the file name for the main attachment (the generated report). After this the second larges change is that all message lines marked as skipped (the property is set to SkippedLine) will no longer be written to the database table by default and instead only stored in-memory during the execution. You can on a per-mapping enable the SkippedLines to be written again if necessary for debugging purposes or any other reason. This will provide a not so insignificant performance boost for message generation and the system will no longer consume as many entry numbers in the message line table. ## Changelog * Attachments now have the correct flag set when posted to the Cloud Integration Platform. * Add filter so "SkippedLines" will no longer be written to the message lines table unless explicitly included on a per-mapping basis. * Reduced locks in Extended Platform and limited the number of messages that can be processed in each job queue execution. * TestMode flag is now cached during message processing. * Migrated to using the new "user-defined layouts" for setting custom report formats with fallback to the old fields. * Use standard Business Central functions to generate e-mail subject and attachment file names. * Updated all translations across the base application. # 24.3 Changelog for Golden EDI version 24.3 that was released on 2024-04-08 ## Description Welcome to our latest release! We've introduced some key updates to improve your workflow and system reliability. ## Changelog * Added support for running codeunits for control validation in control mappings. * Fixed an issue with the message queue processing. * Validate item journals correctly with entry type first. * Fix setup import to correctly clear existing mapping lines. * Truncate item description in GEDI Shipment Advice to handle items with longer names. * Fix filtering in mapping function "Last record in filter". # 24.1 Changelog for Golden EDI version 24.1 that was released on 2024-02-26 ## Description Welcome to another exciting release! This released is packed with a variety of enhancements and features to improve your experience. We've added a "Features Management" feature so we can release previews of new stuff that can be selectively activated to preview upcoming features. This means we can easily release larger changes and try them on a few environments before rolling it out globally for everyone. Before you Go-Live you can now use the "Clear Transactions" button on "GEDI Setup Catalog" page to clear all transaction tables. Best not to use it in production though since it will clear all transactions from our tables and you will lose you statuses and message history. But it's there in case you need it when you want to wipe our tables manually. A new page called "GEDI Setup" has been added and a long with this we added the first configurable setting here which is to control the maximum amount of messages the can be processed in one run of the job queue. ## Changelog * Added feature and setup tables, to allow preview of coming features. * Added button to clear all transactions inside Golden EDI. * Allow truncating before/after import and conversion. * Update the copy mapping to include all fields on the header and lines. * Fix a bug when setting filters to empty strings. * Improve the handling of control documents when no matches can be found. * Allow configuring of number of rows to handle on each run, set to 100 messages as a standard. * Fix a bug where control documents didn't check logs with the correct profile. * Remove all mapping lines for target mapping document when importing setups, to avoid issues with merging. * Run a message as test in the message queue without requiring reset. * Add option to hide profiles from selection lists, by allowing us to mark a profile as a system profile. * Tag first uploaded attachment as the main attachment and all others as secondary. * Open filtered status transactions when clicking GEDI status field. * Added event to PDF function to allow overriding e-mails in our freemium. * Added new XMLBuffer handler for setup packages, not enabled by default for this version. # 24.0 Changelog for Golden EDI version 24.0 that was released on 2023-11-08 ## Description A new release (hopefully) means new stuff and sure enough that is what we have here! In this release we've added some improvements all around the code base and two new features that will hopefully make our platform even more comprehensive. The two primary features we've added is improved handling for invoice discounts and event listeners to the sales return order functionality in Business Central to make sure that we have the same possibility here that we already have for purchase returns. ## Changelog *Golden EDI* * Add query and codeunit to sum discounts per VAT %. * Include query document and lines in clear system function. * Return empty string on text truncation if the starting position goes out of bounds. * Improve handling for sales and purchase return documents. * Add API pages for deep inserts. * Remove dates where possible from setup export. *Extended Platform* * Fix posting of return documents to correctly reset quantities. * Add reference to the source document to intermediate lines. # 23.1 Changelog for Golden EDI version 23.1 that was released on 2023-10-11 ## Description A small release to fix a translation issue in Extended Platform. ## Changelog * Remove a CData element from the Swedish translations for Extended Platform # 23.0 Changelog for Golden EDI version 23.0 that was released on 2023-10-02 ## Description Welcome to another exciting release! We've sprinkled in some neat enhancements and added a nifty API page for system information. Our primary focus has been on paving the way for future data layer updates. Thus, we introduce our brand new System Information API page! The System Information API provides version information for the API contract, our applications and Business Central to our Cloud Integration Platform. This critical information allows our platform to automatically adapt to your specific version by enabling or disabling features. For those of you looking to improve job queue management, you're in luck! We've tackled some persistent heartbeat issues and added a smart feature to ensure that long-running daily jobs won't make unexpected appearances during your workday. ### Job Queue Handling * **Dynamic Job Queue Timing**: We've implemented a new logic that accurately calculates the next expected time a job queue will run. Say goodbye to the 15-minute limitation! Now, you can have job queues with delays far beyond the 15-minute mark without causing unnecessary heartbeat monitoring alerts. * **Precise Daily Job Scheduling**: To make your life a tad easier, we've added a flag for daily job queues that ensures each job starts at the exact same time every day, eliminating any drift. **How it works**: If you set your job to run every 1440 minutes (24 hours), enable this feature, and initially set the job to start at 2:00 AM, the job will continue to start at 2:00 AM each day. This avoids time drifts caused by long-running jobs. **Example**: * **Old Method**: Let's say your job starts at 2:00 AM and takes 30 minutes to complete. In the normal Business Central scheduling logic, the next run would have been calculated as "End Time (2:30 AM)" + "1440 minutes," making it 2:30 AM on the next day. Over time, this can drift further, causing overlap with other jobs or even entering working hours. * **New Method**: With our feature, the next run is calculated as "Start Time (2:00 AM)" + "1440 minutes," ensuring the job kicks off at 2:00 AM daily, irrespective of how long the previous run took. No more surprise visits from your job queue during business hours!

Enable the flag in the picture and the queue will now start at the same time every day.

## Changelog * Check Warehouse Activities requirements when posting transfers in Extended Platform. * Add new option to Method in GEDI Mapping to insert or update with triggers. * Add System Information API. * Add setting that allows logging in imports without the duplicate check. * Add Custom Call 11..20 to Message Selection and Control Message Selection. * Ensure first status ledger entry is always empty. * Add custom "Next Expected" calculations to job queue to better handle long running queues. * Add option to start a daily job queue at the same time every day, avoiding drift. * Replaced legacy views with new views. * Updated translations for Base App and Extended Platform. # 4.8.0 Changelog for Golden EDI version 4.8.0 that was released on 2023-02-09 ## Description The focus for this release has been the new recovery function to ease the handling of recurring errors. There have also been improvements to the handling of sending attachments so we can send incoming documents from non-posted documents. We have also worked on performance optimizations to provide some speed-ups of message generation. This is of course not all but it covers the biggest things we think are important. ### **Recovery Function** A new tool called the recovery function has been added in this release. This utility function allows you to configure automatic retries of specific types of errors. For instance, if you get locks when processing messages you can configure the recovery function to automatically retry the message X amount of times. You can use regex or sub-string matching to filter the errors you want to have the automatic retries kick in. The amount of times to retry a specific error is also configurable so you have full flexibility configuring the system. When a message is under retry it will state so in the column "Message Text", it will also indicate in that text on how many times left it will retry the failure until it considers it a loss. The actual error message will be printed in "Internal Error Text" so you can act on it, if necessary.

Here you can see a message that is "under recovery".

**Configuration** The settings page is where you configure which types of errors should be retried and how many times they should be retried. This can be configured on a per-message-code and per-profile basis so different combinations can be retried a different amount of times despite being the same type of error. You also have the option to use regex which enables fine-grained control on matching the specific error message. *Don't go too crazy though! It can be hard to understand if you go full regex.*

Here you can configure which errors should be retried and how many times.

### Skipped Lines We have elected to hide "skipped lines" by default when viewing contents of messages. Skipped lines are lines that are generated but ignored by both our Cloud Integration Platform and internal processing of messages. You can remove the filter quite easily if you want to see these lines, they can sometimes contain useful information such as filters.

The filter on the left is applied automatically.

Removing the filter will reveal the skipped lines.

### Limit Messages We've added a limit to how many messages we process at one time when the job queue runs. The limit is currently set to 100 but may change in the future depending on need. The reason for adding this limit is to avoid blocking customers job queues for too long. Since only two job queues can run at the same time in Business Central Online across all companies in a tenant we do not want our job to be the reason other might not run. ## Changelog * Recovery functions has been implemented to automatically reset certain types of errors. * Allow incoming documents to be sent on documents other than posted documents. * Remove orphan lines in the GEDI Message Lines table in deletion job. * Fix the cleaning routine for posted and up-auto finished messages to not leave orphan lines. * Limit number of messages to process in one run, the limit is now 100 messages. * Buffer message lines in memory before writing to table in batches. * Added functions to "modify if possible" to tolerate errors when running modify. * Disable editing of entry number in message queue. * Improve handling of modify errors in control to avoid blowing up the job queue. * Hide skipped lines by default when viewing message lines. # 4.7.5 Changelog for Golden EDI version 4.7.5 that was released on 2022-11-25 ## Description The focus for this release has been to work on the Workflow documentation feature. This isn't ready for everyday use yet, but many improvements have been made. We have also added a feature to generate dates/times in filters when exporting, this is useful to limit records that has been changed. Some related and unrelated bugfixes has also been made that improves the stability of the application. ### **Filter Functions** A new toolkit called filter functions has been added to the system. With this you can now run what we call functions before the filter is passed to "SetView" during message processing. This allows you to, for instance, get the current date and subtract two days and use that in your filter to get recently updated records. You wrap the functions with the function block #{...} and it will be evaluated as the system processes the message. You can pipe the output of one function to the next inside the function block by using the pipe '|' symbol between calls. Functions with "Input" in the list below are the functions that can take input from a previous function call. Anything with "Param" expects input from you as the caller. **Functions** * TODAY -> Today(); * YESTERDAY -> CalcDate('-1', Today()); * TOMORROW -> CalcDate('+1', Today()); * WORKDATE -> WorkDate(); * CURRENTDATETIME -> CurrentDateTime(); * FORMAT -> Format(Input); * FORMAT(XML) -> Format(Input, 0, 9); * TIME -> Time(); * DT2DATE -> DT2Date(Input); * DT2TIME -> DT2Time(Input); * <..> -> CalcDate(Param, Input); * TIME(HH:mm:ss.fff) -> Evaluate(Input, Param); * DATE(YYYY-MM-DD) -> Evaluate(Input, Param); * DATETIME(YYYY-MM-DDTHH:mm:ss.fffZ) -> Evaluate(Input, Param); **Examples** ```al WHERE(SystemCreatedAt=FILTER(#{TODAY|<-2D>|TIME(00:01)}) ``` ```al WHERE(SystemCreatedAt=FILTER(#{CURRENTDATETIME|DT2DATE|TIME(00:01)}) ``` #### **Field Look Enum/Options** This release contains a small but very useful addon to the recently updated Field Selection page and that is that you can now find all values for any option or enum in the system as well. This makes it easier to write filters using the integer value of the enum or option you want instead of using the internal caption. When viewing the field lookup page you can now click on the Type column for the row you want to inspect more and if its an Option or Enum you will see a new window open up listing all the different options.

Click the "Option"

And the secrets will be revealed!

## Changelog * Improvements to Workflow. * Filter functions and support for handling those when exporting messages. * Improvements to Shipment and additions for future enhancements. * Fixed a bug in Get Purch. Line where new lines got an incorrectly calculated line number. * Passing RecordRef as var when generating reports in PDF report function. * Renamed Purchase Return Order extension file. * Fixed "Create Message" in Write Message so it gets the correct RecordRef passed. * Added Enum/Option lookup to the field selection page. # 4.7.1 Changelog for Golden EDI version 4.7.1 that was released on 2022-09-28 ## Description This release has been focused on improving the shipment advice functionality in Golden EDI with numerous fixes and general improvements. We have also improved the field selection page used when mapping, so it shows useful information like size, type, deprecation information and more. A new button to fix broken status transactions has also been added. **Field Selections** We have created a new page to handle field lookups when mapping. This makes it easier to identify which fields are usable, which are primary keys, what types the fields are and sizes.

Fields Lookup

**Fix Broken Status Transactions** If you have ended up in a state where unrelated GEDI statuses ends up visible on your documents it can be due to a missing default record in the "GEDI Status Ledger Entries" table. We have added a button that when pressed will fix this issue to get you back to a good state.

Press this button and all your issues will be solved.

## Changelog * Replaced customer name and address fields in Shipment Advice (50 -> 100 characters long) * Replaced external document number in Shipment Advice (20 -> 50) * Added a new page for field selection in mapping. * Exposed functions to release and open shipment advices. * Added Golden EDI fields to purchase return orders. * Added Variant Code to Shipment Advice Lines. * Added a page to view finished shipment advices, they are hidden on the normal one. * Added support for Golden EDI fields in templates. * Added a button to correct the first entry in status transactions. * Fixed some small bugs in the code for Shipment Advices. # 4.2.0 Ändringslogg för Golden EDI version 4.2.0 som släpptes 2021-05-05 ## Sammanfattning Vi har i denna version integration med den nya E-post scenario, optimering utav interna rutiner och på början av arbete för att integrera med våran nya applikation "Golden EDI Extended Platform". #### E-post Scenario Nu har vi byggt in stöd för utskick av PDF genom den nya E-post Scenario funktionaliteten. Vid aktivering av funktionen i Business Central så går Golden EDI automatiskt över till att använda E-post Scenario. Vi stödjer även funktionaliteten att använda olika adresser för olika scenario, så t.ex. Fakturor kan gå med annan address än orderbekräftelse. ![Den använder korrekt scenario beroende på rapportval.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-Mk0zbZYzmetv0c-XHOD%2F-Mk25N6DQXDY1HA6NZoY%2Fimage.png?alt=media\&token=83c3fadd-35cd-4b4f-8eba-0660a2ca3d01) **Workflow** En ny funktionalitet för att dokumentera flöden som är uppsatta i Business Central. Detta ger övergripande blick på inkommande, utgående och kontrollmeddelanden som skapas för de olika profilerna. Det är även möjlig att exportera en Visio kompatibel Excel fil med information för att kunna skapa diagram över flödet. ## Ändringslogg ### Fixat * Sidan Inköpsorder är nu omdöpt till "GEDI Inköpsorder" så att man tydligare ser att det är våran sida och inte en standard sida. * Orderimport kontrollerar nu både standard blockering och den nya blockering utav artiklar. * Filtrering av artikelnummer vid beräkning av moms i den nya momsberäkningen, så man t.ex. kan exkludera avrundning. * GEDI Inköpsorder sätter nu färger korrekt på "GEDI status" så som det är i "GEDI försäljningslista". ### Ändrat * GEDI Queue Handler använder nu query för att få ut meddelanden som ska köra i ett svep. Detta har även kompletterats med publicerade events så man kan lägga till meddelanden som ska köras och även ändra filter som används för att hitta vilka meddelanden som ska köras. * Flera "Manuella Event" är tillagda i meddelandevalen så att man kan koppla på fler skräddarsydda events genom extra appar. ### Tillagt * Funktion för att hämta ut GEDI-profil vid skapande av meddelanden i kontrollfunktionen. * Man kan nu ändra koden i utgående meddelanden, för att till exempel vända ett meddelande så att det går att importera i en annan tabell. * Integration med den nya E-post Scenario funktionaliteten med stöd för dynamiskt valda e-post addresser beroende på "scenario". * Stöd för GEDI status färger på våran inköpsorder lista precis som det är i våran försäljningslista. * Tillagt GEDI Workflow för att kunna dokumentera flödena som är uppsatta i systemet, med stöd för att exportera till Visio. # 4.3.0 Ändringslogg för Golden EDI version 4.3.0 som släpptes 2021-08-25 ## Sammanfattning I denna release har vi fokuserat på att bygga ut grunden så våran nya applikation "Golden EDI Extended Platform" kan koppla sig mot "Golden EDI". En annan stor fokus har lagts på att byta ut och ersätta en stor del av anrop mot de metoder som Microsoft har deprecierat. #### E-post Scenario Vi har tagit bort en del frågor i den assisterade konfigurationen för PDF-fakturering. Detta är för att vi, vid aktivering av E-post scenario, inte tillåter möjligheten att överskrida den utgående e-mail adressen utan vi låter E-post scenario helt ta hand om detta. ![Nu kan du bara sätta utskicksspråket vid PDF-faktura uppsättning.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-Mk0zbZYzmetv0c-XHOD%2F-Mk25kVuJyf7Lg8vtK9s%2Fimage.png?alt=media\&token=60836b6e-9390-42d8-bec7-bfda68a23430) **Skicka meddelande från jobbkö** Där finns nu en kodenhet "70618584 - GEDI Send Partner Information" som kan tillkallas direkt från jobbkön som kan skapa den eller de meddelande kod som ligger under val "Försäljning - Partnerinformation". Detta tillåter till exempel schemalagda utskick av artikelinformation med mera. ![Kodenheten kommer skapa den eller de koder som ligger här.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-Mk0zbZYzmetv0c-XHOD%2F-Mk25xdZsYAQgI_41rhJ%2Fimage.png?alt=media\&token=877e9208-3e22-4c79-8a4f-61d64718ad82) ## Ändringslogg ### Fixat * Ändringar som krävs av Microsoft är nu helt åtgärdade, b.la. Implicit With förbjudet. * Borttagning av onödiga val i uppsättning för PDF. * Tagit bort referens till deprecierad funktion för batch processande av inköpsorder. * Städat upp kod som inte används. * Valet "Kör kodenhet med retur" kan nu köra lookup som "Kör kodenhet" i mappning. * Query kan nu köras även om den är satt under utveckling. * Status är tillagt på sidan för bokförda utleveranser. * Kontroll för dubbletter när man skapar meddelande genom standard arbetsflöde. * Borttagning av validering av meddelandekod vid import av uppsättning. * Workflow kan nu skapas genom rad och inte bara knapp. # 4.1.0 Ändringslogg för Golden EDI version 4.1.0 som släpptes 2021-03-08 ## Sammanfattning Vi har nya funktioner för att hantera överföring och servicedokument. Det finns även med en del fixar och interna förberedelser för nästa version. #### Servicedokument Det går nu att sätta upp kontroll och hantering för servicefakturor och kreditnotor. Viktigt att veta är att servicedokument använder den nya query funktionen för att göra momsberäkning vid utskick. ![Meddelandeval för servicedokument tillagt](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaRKvYXXQm4Qzz3ZgQ%2F-MVaX-FqdZXsI4hdla5E%2Fimage.png?alt=media\&token=9f4ef39c-cd09-4b69-8e1a-a61490c24a52) ![GEDI-fält tillagda på både faktura och kreditnota sidan.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaRKvYXXQm4Qzz3ZgQ%2F-MVaXciobL1CVLVvBUS1%2Fimage.png?alt=media\&token=bcc64361-464c-4753-8179-b8c69efe7ac8) #### Överföringsorder Det går även nu att sätta upp hantering för överföringsorder vid släpp, bokföring och inleverans. ![Meddelandeval för överföringsorder](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaXyT1dJPNXLuB6g5i%2F-MVaYNUXZ-y8qJbr07j1%2Fimage.png?alt=media\&token=93e51cea-092c-4adf-8bc8-e6860591b7a1) **Uppsättningskataloger** Synkronisering utav uppsättningskataloger ger nu bara senaste versionen. Det går att ändra på en specifik profil om man även vill ha ner äldre versioner vid synkronisering. ![Listan är lite mindre nu när bara senaste versionen finns.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaXyT1dJPNXLuB6g5i%2F-MVaYpy6-KvXH431NAPo%2Fimage.png?alt=media\&token=313e1231-46ed-4bb5-bdf9-42630061e17b) På profilen kan man klicka in "Synkronisera gamla kataloger" om man vill ha äldre versioner. Tänk bara på att det blir ganska många kataloger i listan om man väljer detta. ![Kolumnen för att ändra beteendet vid synkronisering.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaXyT1dJPNXLuB6g5i%2F-MVaYwHHvTHup4wpHvr5%2Fimage.png?alt=media\&token=71283c5f-9646-4095-8cf0-7e2255e27ab5) **Statustransaktioner** På sidan "GEDI statustransaktioner" finns nu en knapp, "Ny", för att skapa en ny statustransaktion till ett dokument. ![Knappen för att skapa en ny transaktion.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaZIa7Edjln9uDGOIq%2F-MVaZemfEB9UvVA_sDPw%2Fimage.png?alt=media\&token=941a933f-caf7-428f-bbb6-38c1877890dd) Trycker man på den så får man upp ett formulär där man får fylla i all den information som behövs för att, på korrekt sätt, skapa en ny statustransaktion. ![Dialogrutan som behövs fyllas i.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaZIa7Edjln9uDGOIq%2F-MVaZq46vmD1y2dQjtGU%2Fimage.png?alt=media\&token=6a467a91-8c81-41c9-9530-8258a2538c43) Det går alltså inte längre att direkt modifiera denna lista som tidigare, detta då det lätt kan leda till problem med felaktigt skapade transaktioner. Denna ändring innebär också att vi har lagt till en egen knapp för att ta bort transaktioner i fall man skulle behöva det. ![Knapp för borttagning av markerade transaktioner.](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MVaZIa7Edjln9uDGOIq%2F-MVa_7HgcK-H0aPx_dek%2Fimage.png?alt=media\&token=e66e0298-92db-401d-8ac3-5de70967bd01) ## Ändringslogg ### Fixat * Konvertering mellan datum, datumtid och tid sker nu automatiskt vid import. * Kommentarer för artikelrad kollar nu efter existerande kommentarer. * Fixat en bugg som orsakade att mappning inte hämtade korrekt titel för fält och objekt. ### Ändrat * Släpp av order hanteras nu inte längre för order med förskottsbetalning. * Översättning förbättrad för knappar på "GEDI uppsättningskatalog". * Meddelandeval för bokföring av utleverans hanterar nu även samlingsleverans. * Bokföring av försäljningsfaktura kontrollerar inte längre så att orderbekräftelse har gått iväg. * Rader utan klass och inställningsnamn kommer nu få "SkippedLine" satt som inställningsnamn. * Synkronisering av uppsättningar hämtar nu enbart senaste version. * Beräkning utav uttryck kan nu även göras i importmappning. * Kodenheten "GEDI VAT Query" hanterar nu även moms för servicedokument. ### Tillagt * Hantering utav överföringsorder vid släpp, bokföring och inleverans. * Tillägg av GEDI fält till servicefakturor och kreditnotor. * Hantering utav servicefakturor och kreditnotor vid släpp och bokföring. * Funktion för att skapa ny statustransaktion manuellt. # 4.0.0 Ändringslogg för Golden EDI version 4.0.0 som släpptes 2020-11-12 ## Sammanfattning Vi har en del nya funktioner och en del fixar i denna version utav Golden EDI. #### E-mail Logg Den viktigaste funktionen för både er partner och kunder är att det sparas en logg som går att hitta genom att titta på meddelanderaderna för raden med kod "SI-23-PS". ![Markera raden med kod "SI-23-PS"](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MOamXF1i8pQermzGheI%2F-MOao8JfHXdtkhtQj69O%2Fimage.png?alt=media\&token=4073c200-c709-4593-b261-1b4b3f1c83f1) ![Tryck på "Show Message Lines" / "Visa meddelanderader" under "Report"/"Rapport"](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MOamXF1i8pQermzGheI%2F-MOao5RS4cbkObye-5ol%2Fimage.png?alt=media\&token=a20fab7b-85b6-4501-b010-93296b977b42) ![Denna logg finnes i meddelanderaderna](https://2565746460-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MEXyGMFfvfLDNKk0gaK%2F-MOamXF1i8pQermzGheI%2F-MOaoIky-yUY68yQQQTA%2Fimage.png?alt=media\&token=f1686b98-3160-41ce-8cf0-adf32e296fdb) Här dyker upp information kring vilket dokument, om den har bifogade dokument, vilken adress den skickades till, med mera. ## Ändringslogg ### Fixat * Artikelbeskrivning läggs nu fram i konverteringsdokument om typen är satt till "Artikel". * Text som är längre än fältet smäller inte längre vid inläsning när man använder trunkering. * Funktionen "Bifoga bilagor" läser nu profilen från meddelande kön istället för kundkortet. * Låst mappning kommer nu istället att fråga om man verkligen vill ta bort istället för att helt stoppa. * Fel vid kontroll kan nu rapporteras via e-mail, precis som fel vid import och export. * Delat på meddelandevalet för påminnelse så att kontroll och utskick ligger på olika. * Första dokument som läggs i inkommande dokument vid import markeras nu som huvudtillägg. * Det går nu att öppna försäljningsordern genom att trycka på raden i GEDI försäljningslista. ### Ändrat * Funktionen för konvertering är flyttad till ny kodenhet och samma används nu för både inkommande och utgående mappning. * Funktionen för trunkering av text är flyttad till ny kodenhet och samma används nu för både inkommande och utgående mappning. * Funktionen "Kör meddelande som test" fungerar nu även för koder som är inställda med "Postning". ### Tillagt * Funktion för att generera OCR nummer tillagt i mappning. * Möjlighet att konvertera vid kopplad rad i mappning för inkommande dokument. * Möjlighet att kalla på "Queries" i mappning vid export utav dokument. * Möjlighet att kontrollera värde och antal rader vid import för att kunna stoppa dokument som har fel. * Möjlighet att lägga till kontrollvärden när dokument exporteras. * Det går att direkt skjuta iväg ett meddelande från kön genom att trycka på "Skicka meddelande". * Vid PDF-utskick via intern SMTP så genereras nu rader med information kring utskicket, så som e-post address och rapportnummer som använts. * Appen rapporterar numera till våran Application Insights vid eventuella fel och även till viss del under användning. Detta så att vi kan ha koll på hur produkten används och vilka fel som uppträder under vanlig drift. # Welcome Welcome to the Golden EDI documentation. In the left menu bar at the top you can select the documentation for your NAV version. Please note that we support earlier Dynamics NAV versions as well (from Dynamics NAV 2009 R2) but we do not have the documentation for these versions online, please look at the documentation for NAV 2017 and if you can't find your answer there you can contact our support. # Switch to OAuth A quick guide on how to switch from Basic Authentication to OAuth {% hint style="info" %} This switch from Basic Authentication and OAuth only needs to be done for environments that has a connection to the Golden EDI Cloud Integration Platform. This means that Basic Invoice and Freemium is not affected by this change. {% endhint %} With the removal of Basic Authentication (also known as Web Service Access Key) in the upcoming release "Business Central 2022 Release Wave 1" all connections between the Golden EDI Cloud Integration Platform and your Business Central environment needs to switch over to OAuth in order to not be interrupted. {% embed url="" %} Link to information about the removal of Web Service Access Keys. {% endembed %} In order to do this you need to grant our Azure Active Directory Application access to your Business Central environment. The step to grant this access is a manually step that needs to be done in your system by you or your partner with a user has SUPER or SECURITY permissions in Business Central and is an Active Directory administrator for the current tenant. #### User Prerequisites * [ ] SUPER or SECURITY permissions to register and manage users in the current Business Central environment. * [ ] Active Directory administrator for the current tenant. When the above prerequisites has been met you can continue with the steps below to grant permission for our application to talk to your environment. {% hint style="info" %} The Cloud Integration Platform will only have access to a limited set of pages and tables to read and write messages in our app as controlled by the "GEDI Cloud Platform" permission set. {% endhint %} ### Step 1 - Register Azure AD Application The first step in getting this configured in your environment is to go to the "GEDI Profiles" page. ![Search for "GEDI Profiles" to find the page.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FGQ9dGEopWgjdEPfbAge7%2Fimage.png?alt=media\&token=78eccadd-5f3e-401b-b3d8-5f4efa32f73e) Then you open the "AAD" menu and click on the "Register Application" action. ![To register the application you click on "Register Application" under "AAD".](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FwvwKx6zrU8YyipONqeK1%2Fimage.png?alt=media\&token=1f7b7811-8e2d-4fb0-82e1-5390d689a947) This will register the necessary details in "Azure AD Applications" and set the permissions for the application to the limited "GEDI Cloud Platform" permission set. After this has been completed (currently no dialog is shown so it's completed when you can click on anything else) you can click on the "View Application" option to open the card directly or you can go to the search menu and search for "Azure Active Directory Applications" to find the list of all applications registered in your system. ![The list page to view all Azure Active Directory Applications registered.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FHPJJKGoXAVyMF8dHZrP9%2Fimage.png?alt=media\&token=d3aa78a6-4df2-47f3-9f5e-2dc09e4b92c8) ![The list of all registered Azure Active Directory Applications.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2F8cTmdadaa6qJ3MMK2r4B%2Fimage.png?alt=media\&token=2545e243-c9ab-4984-a652-39b37a742a0b) ![The Azure Active Directory Application for Golden EDI Cloud Integration Platform.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FUthxFpPNbkP8DbgpbMYF%2Fimage.png?alt=media\&token=dda1daf2-9790-494d-bdfe-5f754897014c) ### Step 2 - Permissions The registration itself will add limited permissions for the current company you are in but you might need to either extend this to all other companies in the environment or add specific companies to this list. Which companies it needs to reach depends on which companies you one or more active connections to the Golden EDI Cloud Integration Platform. Which companies the application can reach is controlled at the end of the card under the part called "User Permission Sets". Here you can either add new lines for each company you want to grant access to or remove the company name from the line that already exists to allow access to all companies in the current environment. ![List of permissions granted in each company.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FM094Fz6MLKglfrkZxVzO%2Fimage.png?alt=media\&token=56e2c668-288f-42be-96ce-f3eea1f41b41) To remove the limitation modify the existing line by removing the company name. ![The limited access rights now span all companies in the current environment.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FM6nUWIzKyWRaY7s6HRYh%2Fimage.png?alt=media\&token=5d11ca02-09d2-4783-b987-14eebc4672be) Or if you want to grant access only to a limited set of companies you can add new lines as necessary by selecting the permission set called "GEDI CLOUD PLATFORM" and then the company you want to grant access to. ![Adding companies is done by adding new lines with the correct permission set.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FbTlnm7NSK8WA0uwo9YBT%2Fimage.png?alt=media\&token=9b14fc9d-9274-44c8-a875-1dd8f4f070b6) When this is done everything is now ready to request administrator permissions to allow Golden EDI to connect to the environment using the configured permissions. ### Step 3 - Grant Consent The last step inside Business Central that needs to be done is to grant consent to the application and this is done by clicking one the "Grant Consent" button up in the top left corner of the Azure Active Directory Application Card for the Golden EDI application. ![Click on Grant Consent to start the process.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FrHDciD4f6FbWt9b6vtqN%2Fimage.png?alt=media\&token=2a685bfd-4715-4d45-9556-f2ca53857da0) {% hint style="warning" %} This needs to be done with an Active Directory administrator account, otherwise it will fail. {% endhint %} Clicking on this button will start the process and open up a new window where you can select a different account or the currently logged in account. To continue select or login with the Active Directory administrator account. ![Select the account to proceed with the process.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FO3bUxmnUvHwlfaPYtPOH%2Fimage.png?alt=media\&token=0e043497-9b34-4978-9f18-9ff56b849360) Then you will be requested to review the application and either accept or reject the application. To continue and accept that the Golden EDI Cloud Integration Platform will be able to talk to your system click on the blue "Accept" button down the right corner. ![Click on Accept or Cancel.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2F0E0UfMB4wja2ZhGhLr0p%2Fimage.png?alt=media\&token=50e48499-d06a-4f29-afc8-60249fc49378) If everything works as it should then the extra window should close and you should be sent back to Business Central with a dialog window that says that the process succeeded and that consent has been given. ![Consent has now been given to the Golden EDI application.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2Fw2aMMz7ukSFLaZCURbzP%2Fimage.png?alt=media\&token=e1f58372-2dc5-4451-8a52-a9c9b5a069dc) ### Step 4 - Contact Golden EDI Now you have prepared the system to accept authentication from the Golden EDI Cloud Integration Platform using OAuth instead of Basic Authentication. In order to move over to this the last thing that needs to be done is to notify us Golden EDI that you want to switch over and that your environment has been prepared according to this guide. You need to send the following details for each company in the current environment that has active connections to us at and we will take care of the rest. * Your organization name. * The list of companies in Business Central. * The list of all connections in all companies that needs to be switched over. The details over which connections are enabled and configured in the current company can be found by going to the "GEDI Profiles" page and checking the column "GEDI Connection ID". ![Here we have one connection called GEDIDEMO-STDAPPSOURCE-ICRECV.](https://785456668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVO7c8MSQ0ieazusCSE-3140760735%2Fuploads%2FmJHlw4cVo10ca3sIcTiU%2Fimage.png?alt=media\&token=d8a4a314-9848-4e8d-ad67-5d14fae23cbb) When we have received the information we will make the necessary adjustments in the Golden EDI Cloud Integration Platform and notify you when the switch has been made. If we run into any permissions issues or notice any other problems we will get in touch with you and/or your partner. {% hint style="info" %} This entire process needs to be repeated for any unique production and/or sandbox environment you have that needs to have working connections to the Golden EDI Cloud Integration Platform. {% endhint %} --- [Next Page](/llms-full.txt/1)