Problems with sub-items and header attributes in complains

Question

Hello Gurus!
I am relatively new to the enterprise services and I have a requirement to create a complain with one product and a child product (items 1000 and 1010) but I tried several ways the service and no matter what I do I always get 2 items without relationship between them. I have tried specifying the parent item ID during create (did not expect to work as parent has also not been created yet) and also tried the BusinessTransactionDocumentReference, but also did not work or did not use the content correctly, in the ES Workplace there is not much info about the possible values for this data segment and it's not returned when I read an existing complain (so I think it is not the way to go)
Finally, the question is... can I create a complain using the enterprise service CustomerComplaintCRMCreateRequ and with the header, item and subitem in the same step or must I create first and then update? (Like the manual process would be)
Thanks!

Answer 1

Hi Milos,
If nothing at all has synchronized, I would first double check your connection settings and passwords.
If the synch appears to to be connecting correctly, you will need to look at the data that it is failing on.
The synch queue is the prx_transaction_queue table in the Business One database.  The object_type column refers to a Business One object.  2 for business partner and 4 for items.  The list_of_cols_val_tab_del is the key in the associated table.  For business partners that is OCRD.CardCode and items OITM.ItemCode.
First determine that there is no bad data in the queue.  Bad data is typically defined as null or empty strings in the list_of_cols_val_tab_del column.
Try running the following for business partners:
select *
from prx_transaction_queue
where object_type = 2 and (list_of_cols_val_tab_del is null or list_of_cols_val_tab_del = '')
And this for Items.
select *
from prx_transaction_queue
where object_type = 4 and (list_of_cols_val_tab_del is null or list_of_cols_val_tab_del = '')
If there are nulls or empty strings in the list_of_cols_val_tab_del column, delete them.
If not, take a look at the first records in the queue.
select top 1 *
from prx_transaction_queue
where object_type = 2
order by tmstmp
and for items:
select top 1 *
from prx_transaction_queue
where object_type = 4
order by tmstmp
Change the transaction_type to "X" (remember what is was, because you will need to change it back).  Changing this value will remove the item from the synch.
Rerun the synch. 
If it runs at this point, there is probably data in the records that the synch was not expecting.  The business partner data will need to be examined.  Tics in key values (CardCode, Address Name, contact name, itemcode) may cause problems.
If this is the case, you might want to contact support to try to track the problem down.
Another source of problems may be database collation.  We can talk about that if none of the above works.