GEDI Setup Catalog
"A 'GEDI Setup' is an XML file containing a complete GEDI configuration package"
Last updated
"A 'GEDI Setup' is an XML file containing a complete GEDI configuration package"
Last updated
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.
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.
'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.
Never import a 'GEDI Setup' if you are not sure what its purpose is, you always run the risk of overwriting existing GEDI configurations!
'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.
