From my understanding the way the custom/config specific property --> Data Card --> Variable works is as follows.
- Create file with properties
- Check that file in
- Check-In looks at the data card and finds the fields needed
- Check-In goes to the file and looks for those values
- Check-In then writes the values from the file to the SWPDM variables
- File is then checked in and the custom properties or config specific properties show up on the data card.
If you check in a file that has no custom properties then nothing shows up in the data card.
In your situation you removed the properties from the file so there is nothing to modify the data card variables with, so the information that was there remains there.
You need to put the property names back in with a blank value. The check-In should then be able to write the null value to the variable and show blank on the data card.
This did the trick. Checked the files out, ran #TASK with a custom property task that cleared the values from all configurations rather than remove them, and then the rest of the process worked perfectly!
For anyone else interested I should caveat this by saying that making the configuration specific properties empty ruined our title blocks. So we needed to empty them and then delete them. This gave the desired result for our PDM tasks and the title blocks.
We ran into a similar issue with the values needing to be the same from @ to Config Specific. We wound up copying the Custom (@) Properties to all of the configurations. Have to watch out for library type parts though where all the configurations are different sizes with different properties..