Hi @Rebecca Marks? ,
With this type of issue with the old data attribute definitions within the spatial repository returning, this is pointing to spatial repository permissions or cached responses; given that you no longer seem to be able to regenerate all files within the spatial repository.
You mentioned that you can upload the data with another table name, map name etc if you then alter the attribute columns in the tab file and upload again does the same error occur with the map uploader tool.
Hi @Duri Bradshaw even if the layer configuration is removed from the repository this is occurring, doesn't the volatile setting only affect the attribute columns definition of an existing table/layer.?
I'm really surprised that if you remove the named table, layer config from the spatial repository that you cant upload the table again with the same name etc.
I think this is moving outside the scope of this forum and is best handled by PB support, I'm sure they could do a remote session and look at pertinent logs and the repository itself, including the role permissions within the management console.
You may need to think about the last time you took a backup of your repository and the possibility the repository needs to be replaced.
cheers