I discovered a few permissions that were no longer required so I went back into my security project, deleted the permission and then redeployed the security data using the deployment wizard.

When I went back into role based security on my test application (user version), I noticed that the permission still exists under my roles and I can still assign the permission. (I do not show the permissions tab in the end user version of security)

Is there anyway to remove this permission during the data deployment phase?  I also noticed the same problem with deploying standard data sets.  If I decided to remove data from the standard data deployment set, I cannot remove the data from the destination database, assuming the original data had already been deployed.

Is there a flag I'm missing when creating the deployment packages that will handle this?

Thanks,
Tim

This is something that we have run into ourselves recently.  At the moment the DDT only overwrites the PKs that exist, but does not remove any previous values.  This gets very complicated when you start removing items from the list because of all of the foreign key constraints.

We have discussed adding a deployment option in the DDT to "Flush then Overwrite" which would remove all of the records before adding any item data back in....but we have to thoroughly work through this process before we make a brash change because we need to logically work through the process so that all data integtrity is kept in check.

For the moment, we have just been bringing up the SQL Server Management Studio and manually removing the records.  But there is a legtimate need for this to be automated...we are just working on the best way to approach this.  This will not be available until 1.6.2 or so.

"Flush then Overwrite" is exactly what I'm looking for to handle my standard deployment data, but I can see how you would have to think it through for other circumstances such as permissions etc...

I will figure out a work around for now.

Tim