Additional Resources

The NAS clean-up is a background service for deleting orphaned document links, where the document in Therefore™ was deleted. This is achieved by running REST calls against the Therefore™ to verify if a certain document still exists.

This is a time-consuming process and needs to lock the Therefore-Documents table in BC, so it’s recommended to let it run overnight or outside of working hours.

 

There is no differentiation between documents in recycling bin and files that were actually deleted from disk. So, when a document is restored in Therefore, the link will not be restored in BC Connector.

 

It is mandatory, that the Therefore user specified in the Home Tab, has “view in hit-list” permissions in all categories, that need to be checked.

 

The NAS clean-up job is an optional feature and needs to be set up under Setup->”Setup Job Queue”:

 

Click on New to create a new job:

 

•As 'Object Type to Run' choose 'Codeunit'.

•As 'Object ID to Run' choose '52101156' which is the Therefore™ NAS clean-up.

•As 'Parameter String', the value 'maxMinutes=240' can be configured.

 
If 'maxMinutes' is set, the clean-up will be done in chunks. The configured “Starting Time” and “Ending Time” will not cancel a running NAS Job.
Because of that, the 'maxMinutes' parameter was added, to limit how long the task will execute. The task will remember, on which Link-ID it stopped and will continue from there on the next execution:

 

When everything is configured and a start date is set, the status needs to be set to ready:

 

In case something has gone wrong, you can either click on “Show Error” on the Home-Tab or check the logs in the “Job Queue” Tab under “Log Entries”: