Azure DevOps WIQL Synch missing items

Hi ​@casey.h,

Thank you for posting in the Lucid Community! Do you mind providing screenshots of the issue you are running within the steps so I can investigate further? If you prefer to share these screenshots in a private support ticket, please let me know and we can continue troubleshooting within an email thread.

The WIQL screen shown below has 54 total records. Only 50 are shown on the first page:
 

If I click ‘synch’ from this screen, it will remove the work items from the dynamic table that are not shown in the first 50 records:

If I go back to that WIQL screen, page over to the remaining work items, and hit synch:
 

It will re-add the work items into the dynamic table:

Clicking the synch button from the dynamic table options also removes any work items that are not in the top 50 records:

Hi ​@casey.h,

Thank you for providing those screenshots! If you don't need to purge old items from the table, can you try unchecking the "Remove non-matching ADO work items from this Dynamic table" before clicking Sync? This should prevent the tool from deleting the records from that 2nd page. Please let me know if this issue persists or if you need to keep this checkbox selected when syncing the items.

If I deselect “Remove non-matching ADO work items….”, then it won’t maintain the table according to the query, correct?

For example, once a work item is ‘Closed’, it is supposed to get removed from the query/table as the query is meant to represent only active and future work items.

Hi ​@casey.h,
 

Thanks for the reply! That’s correct, it will result in a more manual cleanup process. I am unable to reproduce this error, can you confirm if you are experiencing this issue on only this table? Or is this an issue you have experienced whenever your query pulls up more than 50 work items?

Could you share a temporary Document Support PIN for this document AND a technical support PIN for your account? This will help me take a closer look at what’s going on. These PINs are safe to post in this thread because it is only accessible by members of the Lucid support staff. You can find steps for generating Support PINs in this Lucid Help Center article: Generate a Lucid Support PIN.

It appears to be happening on both tables that I’ve tried. Seems to be an issue with any query that pulls up more than 50 work items.

Unfortunately, the above example query is now below 50 items, but here is a General Support PIN for another query/table (102 work items) that is exhibiting the same behavior: duMHU2jMWjjbKhnI1QOh0hKvslHUoR370Y155466768.

Technical Support PIN: iudkZIgmGW9cR1tdTQq7CKEqA5EbMMcvgk155466768