Hi,
I recently updated to a new version of Mobile Card Builder (21.5.0). After doing so, I'm unable to delete containers (or really, anything) in a card template. This only happens if there are cards using the card template.
I assume the new version of Mobile Card Builder does this to prevent someone from deleting an object in a container, and then therefore triggering a cascade deletion to the field mapping on the actual card. This makes sense in a specific setting, but it's very tedious if you're just developing a template and a card.
With the change, my development process looks like the following:
1. Create card template
2. Create card from template
3. See that I need to change something in the template
4. Open the card, change the template of the card to something random since I can't edit the card template otherwise
5. Make changes to the card template
6. Open the card, change the card template back to my template
7. Re-do all field mappings on the card
8. Test the result
9. Realize I need to change something in the template
10. Repeat everything from step 4
Whereas before, it would be like this:
1. Create card template
2. Create card from template
3. See that I need to change something in the template
4. Open the card template, make my changes
5. Re-map only the field mappings I've changed in the template on the card record
6. Test the result
7. Realize I need to change something in the template
8. Repeat everything from step 4
Is there any way to turn this protection off? As I said above, I get why ServiceNow would add something like this, it's just very unpractical if I'm the only mobile developer and the application isn't even live yet.
