locked
Custom entity fields deleting for no apparent reason RRS feed

  • Question

  • I have a custom entity I have created call "Machines".
    I have a workflow that when the "Machines" lookup field in "Orders" contains data, that information for the "order" is put into the fields of the selected "machine". As the "order" "status reason"  changes the "machine" get update too.
    The problem is that ocansionally the order information is being deleted from the machine. In this workflow there are 2 steps that have "clear" functions associated with those fields, however, the conditions for them to do this are not met. Besides that, there are fields that do not have the "clear" function assciated with them deleting. All of these fields are on the same tab and all are filled with information for the "orders" entity.

    I currently have Javascript running, SQL script running and Workflows running against the Orders Entity.

    Any help would be greatly appriciated....

    Thanks

    Scott Coates
    Technical Specialist
    North America Traffic Inc.
    Tuesday, June 16, 2009 3:39 PM

Answers

All replies

  • If you notice the machine is missing data soon after the deletion occurs, you can review the workflow log to see which workflow rule removed the data.  If you are not sure whether it's javascript or the workflow or the sql script which is deleting the data, i would add an audit field (ntext) to the machine form and then in every workflow step where data is deleted, append to that audit field with a timestamp and workflow name so that you can narrow down when the data is being deleted.  Also, you can add javascript to the onchange event of that field on the machine form to also write to this audit field in case the data is being removed manually.

    Tuesday, June 16, 2009 3:46 PM
  • There about 4 workflows running against the machines doing various things, but there are fields not associated with the workflows being deleted too. My though was user error, but it happened on 3 random machine records all assigned too different people and all at the same time. Their is no connection between the machine records only that they are all part off the machine entity.

    To add a bit more information that I just recieved, It is changing the Machine status reason which is set to match the order status reason, plus is changes some bit fields too.

    Thanks
    Tuesday, June 16, 2009 4:04 PM
  • A bit field, huh?  Review this kb and see if it fits your scenario:  http://support.microsoft.com/kb/949732

    Tuesday, June 16, 2009 4:09 PM