InfoPath Dev

Hello

When admins delete a file from WSS, it also delets the file from DBXL, so there is no problem at all.  But I have noticed that when users delete a file from WSS, the Propagate Delete feature of DBXL (v2.3) is not working.  I am wondering if the configuartion of DBXL in a server has something wrong or it is a nature in the current version.

I have copied the error log in the evet viewer in the server.

-----------------------------------------------------

Caught exception obtaining SPListItem for known item in list (item was probably deleted from SharePoint by someone other than DBXL) http://<server name>/TestForm (DocType = 'TestForm', DocId = 2955)

System.ArgumentException: Value does not fall within the expected range.
   at Microsoft.SharePoint.SPList.GetItemById(Int32 id, String strRootFolder, Boolean cacheRowsetAndId)
   at Microsoft.SharePoint.SPList.GetItemById(Int32 id)
   at Qdabra.Dbxl.Domain.SharePointObjectModel.Delete(SharePointListItemMapping mapping, SharePointDocumentData doc)

The stack trace was:    at Microsoft.SharePoint.SPList.GetItemById(Int32 id, String strRootFolder, Boolean cacheRowsetAndId)
   at Microsoft.SharePoint.SPList.GetItemById(Int32 id)
   at Qdabra.Dbxl.Domain.SharePointObjectModel.Delete(SharePointListItemMapping mapping, SharePointDocumentData doc).

----------------------------------------------------

Hello:

Do your users have permissions to delete xml for that document type in DAT? Open the DBXL Admin Tool, and edit the TestForm document type. Look under the Permissions tab -- are you enforcing permissions? Do your users have the right to delete? An overveiw of DBXL permissions can be found here.

Hello

Thank you for the reply.  I have set "delete" permission to users in the DBXL Admin Tool, and now deleting a file from WSS can delete the file from DBXL too.  I am wondering if we have to set permissions whenever we create a Form Library in WSS or we can set a default setting in web.config file which allows users to delete a file from WSS and DBXL?

Thanks

I think you'll need to set the permissions individually for each document type -- creating an Active Directory group can be a way to streamline this. Since your license allows for only 5 different document types, I don't think permissions set up will be too burdensome. Also, in DAT, under the permissions tab for a document type, you can copy the table and paste it into another document type as well -- this may also make this easier.

I've asked the rest of the group if there is a way to configure this globally -- if so, I'll post back or someone else will with more information.