All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
It is not possible to use the standard column "ID" in the where clause of a process post as the underlying loop tables are mapped with the parent loop table via the field ParentID and not with the field ID.
Integrate doesn't take this into account when applying the where clause.
Please find attached a detailed description of the problem and solution proposal.
Further info in support ticket https://support.syniti.com/hc/en-us/requests/24730.
A work-a-round is adding a new field in the upload tables/views in order to use this field in the "where clause".
Add new field in all auto generated upload tables. Example LoadSeqNr
Initialize the new field
For the parent loop use field ID
update ttBP_Maintain_BAPI_BP_MAINTAIN__Upload set LoadSeqNr = ID
For the child loops use field ParentID (is same value as in ID-field of parent loop)
update [dbo].ttBP_Maintain_BAPI_BP_MAINTAIN_Address_Header_Data_Upload set LoadSeqNr = ParentID
Add the field into the upload views
Bert Willekens
Quicker work-a-round would be to add the field ParentID in the primary loop view and fill it with the ID-field.
Attachments Open full size
Bert - thank you for raising this topic. We'll discuss this with our engineers and advise of the outcome.
Attachments Open full size