I'm loading the MIGXdb formtabs directly from json now, as you explained in issue #296. So far it works, but I was wondering if the migx_id values for each field still need to be unique when using this with method.
Because I noticed that when using the MIGX CMP, these values are autoincremented and also corrected again if you're importing an updated config back into the CMP. But maintaining this index manually is of course not very desirable and so far I don't see how these IDs are referenced or used. Setting everything to "MIGX_id": 1 in the json config still loads the grid correctly and displays the output correctly with migxLoopCollection.
I'm tempted now to ignore these values, but I'm pretty sure it will get me in trouble at some point. Can you see already where?
Hi Bruno,
I'm loading the MIGXdb formtabs directly from json now, as you explained in issue #296. So far it works, but I was wondering if the migx_id values for each field still need to be unique when using this with method.
Because I noticed that when using the MIGX CMP, these values are autoincremented and also corrected again if you're importing an updated config back into the CMP. But maintaining this index manually is of course not very desirable and so far I don't see how these IDs are referenced or used. Setting everything to
"MIGX_id": 1in the json config still loads the grid correctly and displays the output correctly with migxLoopCollection.I'm tempted now to ignore these values, but I'm pretty sure it will get me in trouble at some point. Can you see already where?