Problem
After txc env solution import, customizations are NOT published. The developer must remember to run txc env solution publish separately. If they forget (or if publish fails because the import is still running async), the changes don'''t appear in the app.
During testing, this caused significant confusion — form changes were imported but not visible until manually publishing.
Recommendation
Either:
- Add
--publish flag to txc env solution import that auto-publishes after import completes
- Or at minimum print a reminder: 'Import queued. Run
txc env solution publish after import completes to make changes visible.'
Related
The async import + publish race condition is also problematic — publish fails with 'Cannot start PublishAll because Import is running'. The CLI should wait for import to complete before attempting publish.
Problem
After
txc env solution import, customizations are NOT published. The developer must remember to runtxc env solution publishseparately. If they forget (or if publish fails because the import is still running async), the changes don'''t appear in the app.During testing, this caused significant confusion — form changes were imported but not visible until manually publishing.
Recommendation
Either:
--publishflag totxc env solution importthat auto-publishes after import completestxc env solution publishafter import completes to make changes visible.'Related
The async import + publish race condition is also problematic — publish fails with 'Cannot start PublishAll because Import is running'. The CLI should wait for import to complete before attempting publish.