Within the current FortiManager design, CDB handler iterates all targets in one transaction and if ANY addition of EPG fails it overwrites all successful results with the generic error - 'Task failed with error: Data is not committed due to other data's error'.
To find out the reason for the import failure, execute the following commands, reproduce the issue, and save the output in a text file:
diagnose debug reset
diagnose debug application connector 255
diagnose debug enable
In the collected output, search for the 'error' keyword to find the cause under the '__do_cdb_node_attr_check error' function:
__do_cdb_node_attr_check error:firewall address.name ThisObjectIsTheTriggerAsItsNameHasOver79CharactersSoTheFortiManagerWontImportItAsItsBreachingTheNameLengthLimitation
Response [gui json:20989:0bf05148-d2a8-43c2-aa8f-a71ff5b7160f]:
{ "id": "0bf05148-d2a8-43c2-aa8f-a71ff5b7160f", "result": [{ "data": { "name": "NormalObjectNameLength"}, "status": { "code": -1, "message": "Data is not committed due to other data's error."}, "url": "pm\/config\/adom\/FGT_prod\/obj\/firewall\/address"}, { "data": { "name": "NormalObjectNameLength2"}, "status": { "code": -1, "message": "Data is not committed due to other data's error."}, "url": "pm\/config\/adom\/FGT_prod\/obj\/firewall\/address"}]
In the provided example, there was an object named 'ThisObjectIsTheTriggerAsItsNameHasOver79CharactersSoTheFortiManagerWontImportItAsItsBreachingTheNameLengthLimitation', causing the failure of the EPG import as it breaches the maximum character limitation for the firewall address name. See the Text strings section of the administration guide.
| 
