@reginald-grimes wrote:
So the goal is, if I decide to import the "profile_id_left" / "profile_id_right" values from the csv, it would then match the visibility parameters/states that have the equivalent name/number. ...
Believe me, we understand the all that, except the relation of the imported data to the existing blocks is where the confusion is.
Block with LOCATION ID AB202P
Current visibility value of "profile_id_left" is 8 and "profile_id_right" is 10.
Block with LOCATION ID AB205P
Current visibility value of "profile_id_left" is 6 and "profile_id_right" is 2.
If the user run the program, select a block
Change the value only of the current visibility value. in this example change value of 8 to 8 as that is what is specified on the CSV file?
or
Change all "profile_id_left" and "profile_id_right" values [Visibility and Attribute value] and leave the current as it is? meaning the current visibilty has nothing to do with it?
@reginald-grimes wrote:
I would like for the csv to export all block attribute fields with headers. I would also like the csv to contain the block handle.
And that is another task? Will that be the same data that will be use for import and the one you attached is not the final format?