Hello everyone,
We have received the green light to ship our application to production, which is great news! However, I now face the challenge of adding some crucial data to the production environment, specifically, master data such as employee, customer, and product details.
Our application is divided into separate modules, following the Architecture Canvas, namely Employees_CS, Customers_CS, and Products_CS.
I have researched this topic on the forums and found some helpful discussions here:Deploying Data to testing serverBootstrap data during Deployment
My plan is to bootstrap the data from an Excel file that I will create for each module. Instead of using a timer, I am considering using a "Sync Master Data" button on the admin screen. This screen is accessible only by admins and has been created within our application. This button will call all three bootstrap actions to populate the required data. As this will be a one-time action, I don't believe a timer is necessary. However, I welcome any suggestions on a better way to achieve this.
just some loose thoughts :
Hi André,
One suggestion could be to follow the logic that the bootstrap actions have. Before creating any data, check if the table is empty or not, and then, only create the data in the excel file if the table is empty.
This way you will avoid creating duplicated records if any user clicks the button for a second time.
Hope this helps,
Pedro
Thank you for your valuable feedback, it is much appreciated.
@Dorine Boudry I agree with your suggestion to test the logic either in our commercial licensed environment via a separate development module or in my personal environment before implementing it in our application. I do not anticipate there being a large amount of data, as we have only approximately 60 employee records, 20 customer records, and 100 product records.I have already implemented a screen where we can remove data from any entity in the application if needed, but your suggestion regarding uploading a file could be a smart idea. In that case, we would need three separate upload buttons for each module.I will make sure to verify the data being loaded into the application.The data is relatively static, as it is intended to help users get started with using the application without having to manually add each employee, customer, and product. Of course, new employees or products may be added later on, but users can do this within the application as needed.
@Pedro Marques, that is a good point, and we have already considered using an "if" statement as a safeguard to prevent duplication of data, as mentioned in one of the previous posts.