Quantcast
Viewing latest article 2
Browse Latest Browse All 19

New Post: Publish item and link Activity - Should item deletions be cascaded?

Hi Ryan

I have been playing with your Publish item and link custom activity today in Sharepoint Designer.  I am using it on a documents library to publish items out to a duplicate document library.  This is just a test case.

My document library has some custom fields and is designed for uploading existing documents, not creating new documents from templates. When I first started using your activity earlier today it seemed to work perfectly.  I could upload a document, enter the custom field data and when the document was saved, it would immediately be publsihed to the duplicate list.  Updating the document or meta data would equally cleanly update the document in the duplicate list.  Also, I am sure that if I deleted the item from the main document library, that deletion was being cascaded through to the duplicate list with the corresponding item being deleted from the duplicate list.

However, now the activity does not seem to be working correctly and I cannot figure out why.

  1. The activity is still triggering and publishing the item from the document library whenever the source item is uploaded or edited.  However, after uploading a document, if I fill in the metadata and save, I get shown a sharepoint error page indicating that the record cannot be saved because it is currently being edited.  If I don't fill in the metadata the item saves ok and the activity works ok and publishes.
  2. Deleting a published item from the main documents library is now not cascading through to the duplicate library.  The corresponding item is not being deleted from the document library.

In order to try debugging I have updated a view on the main document library to show your "Published To" field.

The duplicate list I am publishing to is located at URL http://data-server:83/tempdocuments/

After I upload a document to the main library for the first time, the activity runs and I see an entry in the "Published To" field of http://data-server:83/tempdocuments/forms/dispform.aspx?id=8;

However, if I look at the duplicate list, the id of the item just published is actually 9.  Is this expected?  This behaviour is seen across all published documents.  There is always an offset of 1 between the published id in the "Published To" field and the actual id of the item in the duplicate list?

The one thing that has happened between the activity working and not working is that wss 3.0 service pack 2 was installed onto our server.  I know there were some changes in sp2 to prevent workflows entering infinite loops due to changes made to the list item by the workflow itself.  Could this be anything to do with why the activity appears to not work now?

I'd appreciate any info as to what may be happening and if what I am seeing currently is expected or unexpected behaviour.

Thanks in advance

Nick


Viewing latest article 2
Browse Latest Browse All 19

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>