Skip to main content

Hi All,


 I was trying to  create a process using the Destination Rule " Plan per slot (no destinations) &  in the destination Rule Options for "select a list field to determine how many slots should be created" I chose the Smart Object " Model Name" since the reminder emails were just generating  for only one item on the list 3 times ( based on the due date) instead of generating 3 seperate emails for 3 seperate items;


Correct me if I am wrong but my step would be to :


Get the items from the SP site; Setup or assign the variables I will be using in my email


but i keep getting the error message " Server was unable to process request. ---> Input string was not in a correct format."


What could be wrong?





Example:
a list has 3 items: A, B, C they all have the same "Targeted Date" so there should be 3 emails sent out that will say A,B,C but instead email gets sent for A, A, A. 
Thanks





 


Hi,


I think this is due to the way you have setup the Destination Rule or the Email Event.


Firstly check the Destination Rule. Make sure the name of the field containing the identifier (A, B, C in your exmple) is dragged into the "Select a list field..." option of the Destination Rule. Make sure your filter here is specified on the "Target Date" field. This value is now saved to the ActivityDestinationInstance.InstanceData field of the Activity.


In your Email event configuration make sure you are filtering the data used in your Email based on the InstanceData context field. The InstanceData field will be the input property to the Load method of your SmartObject and it will return the relevant data which can be used in your Email. A SmartObject Reference might work rather well for this purpose.


Maybe as a reference see the following blog post where I explained something similar: http://www.k2underground.com/blogs/blackbelt/archive/2011/09/02/scheduling-a-workflow-on-several-list-items.aspx. Compare your settings to the ones I configured for the scenario.


Let me know if you could get it working.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings