Suggest an Idea

[paulstevens]

'Select All' checkbox in the 'Import from Project' feature will only select the listed items in the panel if any search result filter is applied.

1. In the project dashboard, manage the model
2. Select the 'import from Project' menu option above the entity list left panel.
3. Select a project to import a project
4. Search for a term and a subset of results is displayed.
5. Click 'Select All' and every item is 'checked' in the displayed search results
6. Clear the search term in the search textbox, and the entire list of entities is 'checked', not just the entities from the search result list.

The expected behaviour is only those items in the search result are selected when 'select all' is ticked with a search result, and clearing the search result term from the search box will display all entities and only those entities ticked (or previously ticked from multiple searches) are ticked.

[TimGarrod]

This is not currently planned as a feature for Compose.   Will leave this ideation open for additional comments. 

[srstage80]

This capability or a similar capability would be helpful in the case of incremental code migrations.  The project deployment process at current is the entire scope, including code that hasn't been changed.

The compare/apply CSV process only supports this capability, conceivably, through a delete/replace approach which would be manual because the apply process cannot update or delete anything.  There every iteration of a CSV migration has to appear as an 'add' to Compose so it will apply.

Desired outcome:

- If I have a Compose project with 100 code assets in it and I only change 3 of them, I need only those 3 things to be promoted into the next environment without having to perform additional steps.  Requiring 100% of the code to move between environments on the smallest scope of change is not efficient and I have to trust that Compose left all the unmodified assets alone.

Impacts:

• Migrations in all projects but most noticeably large projects will be faster
• Testing of changes can be scoped to specific assets instead of entire projects
• No potential risk of unmodified code being modified or corrupted in the migration process

Possible implementations:

• UI feature as noted above
• Enhance CSV compare/apply process to perform an update-merge with the target asset

[Meghann_MacDonald]

Hi, this idea has been in "Not Planned" status for over a year and is still not in consideration. If you'd like to open a new request, please visit the Browse and Suggest page and click "Suggest features" and open a new request.

Meghann