Hi Garion,
to add to what Eric said, the reason why you can't edit that dataview, is because that object does not exist. You can add an on change event to your attribute field, where it checks the value of CorePropertyInformation/Attribute in an exclusive split, and creates the correct object. In this case, if the attribute "Charge" is chosen, you would use a create activity that creates the "Charge" object and associates it to your "CorePropertyInformation" object.
Here is an example of what your on change microflow could look like.
I did a create activity for the value charge, for the other values I just put a placeholder, but you would replace all the merge activities with create activities.
When did you create the "charge" object? Perhaps it doesn't exist? If that's the case, you could perhaps use an on-change microflow to check the existence of and create the correct object.
Do you have read/write access on attributes of the Charge entity? If not then you should set them to read/write.