Based on my experience and
this earlier post, here’s what has worked best for managing plugins and AXP files, while avoiding common pitfalls:
When your database is updated to add an additional column or columns, what do you do with your .axp files in the Plugins/Projects folder?
Always keep your AXP file updated after plugin use
Whenever you use a plugin (e.g., Summary Reports), it modifies the AXP file stored on the server to include plugin configurations.
It's crucial to download this updated AXP file after using a plugin. If you later make structural changes using an outdated AXP and regenerate/upload the app, you risk losing plugin-generated settings.
Do you replace the file with the same filename and an updated schema? Does this cause issues with existing reports? e.g. Summary Reports?
Use versioned AXP filenames if you're making major changes
Replacing the AXP with the same filename is fine, as long as it's the most recent version (downloaded after using plugins). If not, you may lose plugin-generated content. To keep track of changes and maintain a fallback, it's good practice to save dated versions like Project20250708.axp. Moreover, always base new changes on the most recent AXP that includes plugin configurations.
Does updating the project result in loss of visibility of all reports built with a previous version?
No, after DB/schema changes, regenerate and reapply plugin settings
If your schema changes (e.g., adding a column), regenerate the app in AppGini and then open the plugin (e.g., Summary Reports), upload your project file again to refresh the available fields and regenerate the plugin output. This is also when some previously built reports might disappear or break, usually because the underlying schema changed and the plugin can’t find the old fields. That’s not a bug, just a mismatch between schema and config.
Do you wipe reports each time and rebuild them each time? I find that reports built on the old data model sometimes disappear and I have to start again.
No need to wipe/rebuild from scratch each time, unless something breaks
If you've been using the latest AXP and follow the above steps, most reports should stay intact. But if a specific report references a field or table that was renamed or removed, it will need to be rebuilt.
Rest asured Elgaucho, you're not alone. Many users run into these sync issues between schema updates and plugin setups early on. With consistent versioning and careful AXP management, the process becomes much smoother and more predictable over time.
-Saymaad
