Have you ever suddenly realized you are testing the wrong code or data? I have. There is no alternative, you’ll have to do some work all over again. What a waste of time, not to mention the pain of sharing news about the schedule.
Similarly, team members have all committed work, but the integrated test fails. Same results, times x for the whole team.
This is how VSCode can integrate with Git to help avoid those problems.
The import-export tool and AML are reliable, but a bit clunky to use. InnovConfigCE uses the core of these tools to make the work of preparing packages and data more streamlined, fewer manual steps, fewer opportunities for a fumble. It’s the fumbles that cause the problems recognized above.
New in the CE 2025 version are:
1. Documentation is updated and tested for easier to follow setup and use.
2. Steps are now VSCode Tasks which can be run from the Command Palette.
3. Setup Step 0 now simplified, tested and documented in the Setup Guide.
4. From Aras we have ConsoleUpgrade 15, which runs with R14, no longer requiring identical build numbers to Innovator.
5. Main branch is now CE 2025, prior code in CE2024 branch.
Next steps:
1. Seeking more user feedback.
2. Build out Automated tests for InnovConfig setup and functionality.
3. Ditto for PR Workflow.
Join 4-R-Forum and request access to the GitHub Repo.