Currently I am using the Bulk Add Queue Items activity to upload the queue items, I have successfully added a Reference & Deadline to the Datatable with will be uploaded. However, only the reference is getting picked up by the orchestrator and not the deadline. It is as if the orchestrator thinks it is a Specific Data Custom Field.
The header of the column is “Deadline” and the dates are in the formate “yyyy/MM/dd” like the webpage says, however they are not recognised as a Deadline and end up in the Specific Content.
Hi @Harika_Mudiam, what is expected is that the deadline is the actual deadline of the QueueItem and not in the Specific Content.
As you can see the deadline is not shown here in the overview:
@loginerror Any idea on this? Even i am facing the same issue. if the same csv is uploaded directly to queue the deadline gets added but if the same is read as data table and uploaded using bulk add queue items activity deadline is not getting captured
I tried to find more about this issue and have setup the scenario and sadly I had the same issue as others. This happens not only for Deadline as @CasparM and @rahul.lakshmanan found, but this also happens to Postpone field.
System Activity package version 20.10.6 has this issue as well.
Indeed, it looks like we have this bug already registered. The UI tells the wrong story.
For now, please use: DueDate instead of Deadline
and DeferDate instead of Postpone
It should work then
Which says use: OLD — New DueDate = Deadline DeferDate = Postpone
In summary:
The orchestrator UI was updated with Deadline and Postpone as headers. Studio does its job, but orchestartor has no idea as it parses the incoming table looking for the old header names DueDate and DeferDate in the Bulk Add to Queue activity.
Simply put, the bug forces Orchestrator to look for wrong header strings.