...
For this the next steps need to be taken:
- Upload the configUpdateModule config file in the ModuleConfigFiles directory and make sure it is part of a workflow.
- Start an OC and create a replica of the database with config (F12 – Database – replicate central database) time series are not necessary
- Create a SA with the replicated localdatastore without (!) config directory
- Place new version of the active .csv, .dbf and .shp files in the configured import directory
- Start the SA and run de ConfigUpdateModule
- When a new config revision set has been created it will have an id like: "unknown;X"
- If a new config revision has been created, errors can occur due to on the fly config update which a SA can not handle. The errors should disappear after restart.
- Close the SA and restart
- Export the default config (F-12 export – default config)
- Check whether the new .csv, .dbf en .shp files are present.
...