Reltio Connect

We are using the batch API to send organizations to DnB for matching and the DnB monitoring API to import updates from DnB for DUNS numbers that are registered for monitoring.  Both of these are scheduled to run daily and are working fine.

Question for the community is how are you configuring the batch job to register newly added DUNS numbers from the match job for monitoring by DnB (dnb/monitoring/batch)?  It does not seem that the match job automatically registers them    Am interested in what filters you might be using to identify only organizations that have had DUNS numbers assigned in the previous run of the match job to limit the number of organization sent to DnB.

I can run it manually and add a timestamp range for the Vendor Verification Date to pick up organizations recently matched , but this does not lend itself for having a scheduled job that runs once a day.

Thanks.

I'm pinging the PM on this for more information. More to come

We are using the batch API to send organizations to DnB for matching and the DnB monitoring API to import updates from DnB for DUNS numbers that are registered for monitoring.  Both of these are scheduled to run daily and are working fine.

Question for the community is how are you configuring the batch job to register newly added DUNS numbers from the match job for monitoring by DnB (dnb/monitoring/batch)?  It does not seem that the match job automatically registers them    Am interested in what filters you might be using to identify only organizations that have had DUNS numbers assigned in the previous run of the match job to limit the number of organization sent to DnB.

I can run it manually and add a timestamp range for the Vendor Verification Date to pick up organizations recently matched , but this does not lend itself for having a scheduled job that runs once a day.

Thanks.

We are using the batch API to send organizations to DnB for matching and the DnB monitoring API to import updates from DnB for DUNS numbers that are registered for monitoring.  Both of these are scheduled to run daily and are working fine.

Question for the community is how are you configuring the batch job to register newly added DUNS numbers from the match job for monitoring by DnB (dnb/monitoring/batch)?  It does not seem that the match job automatically registers them    Am interested in what filters you might be using to identify only organizations that have had DUNS numbers assigned in the previous run of the match job to limit the number of organization sent to DnB.

I can run it manually and add a timestamp range for the Vendor Verification Date to pick up organizations recently matched , but this does not lend itself for having a scheduled job that runs once a day.

Thanks.

Hi Michael,

Did this answer your question?

We are using the batch API to send organizations to DnB for matching and the DnB monitoring API to import updates from DnB for DUNS numbers that are registered for monitoring.  Both of these are scheduled to run daily and are working fine.

Question for the community is how are you configuring the batch job to register newly added DUNS numbers from the match job for monitoring by DnB (dnb/monitoring/batch)?  It does not seem that the match job automatically registers them    Am interested in what filters you might be using to identify only organizations that have had DUNS numbers assigned in the previous run of the match job to limit the number of organization sent to DnB.

I can run it manually and add a timestamp range for the Vendor Verification Date to pick up organizations recently matched , but this does not lend itself for having a scheduled job that runs once a day.

Thanks.

Not totally.  I was aware of the API but my question was more how to configure the filter in this API to only register DUNS numbers that have been added to our Reltio tenant since the last run of this API.  

Hi Michael,

Did this answer your question?

We are using the batch API to send organizations to DnB for matching and the DnB monitoring API to import updates from DnB for DUNS numbers that are registered for monitoring.  Both of these are scheduled to run daily and are working fine.

Question for the community is how are you configuring the batch job to register newly added DUNS numbers from the match job for monitoring by DnB (dnb/monitoring/batch)?  It does not seem that the match job automatically registers them    Am interested in what filters you might be using to identify only organizations that have had DUNS numbers assigned in the previous run of the match job to limit the number of organization sent to DnB.

I can run it manually and add a timestamp range for the Vendor Verification Date to pick up organizations recently matched , but this does not lend itself for having a scheduled job that runs once a day.

Thanks.

Thank you for your question. If I understand correctly, you're looking to automate the process of registering entities with newly added DUNS numbers. This can be accomplished through filter creation. Specifically, you can filter based on the presence of a DUNS number.

Additionally, I should note that the DnB connector in this case uses an Export service, which in turn relies on a specific Filter system (link to documentation here). After reviewing this documentation, I believe you'll find it easier to configure the filter you're interested in. However, if you encounter any difficulties, feel free to reach out, and we'll be happy to assist you.

As for timestamps, it is possible to incorporate static time ranges into your filters, but currently, there is no built-in functionality for dynamic date filtering for today's or yesterday's dates.

You can combine multiple filter criteria using the and keyword for more precise filter configurations. As a result, your JSON filter might look something like this:

Not totally.  I was aware of the API but my question was more how to configure the filter in this API to only register DUNS numbers that have been added to our Reltio tenant since the last run of this API.  

Hi Michael,

Did this answer your question?

We are using the batch API to send organizations to DnB for matching and the DnB monitoring API to import updates from DnB for DUNS numbers that are registered for monitoring.  Both of these are scheduled to run daily and are working fine.

Question for the community is how are you configuring the batch job to register newly added DUNS numbers from the match job for monitoring by DnB (dnb/monitoring/batch)?  It does not seem that the match job automatically registers them    Am interested in what filters you might be using to identify only organizations that have had DUNS numbers assigned in the previous run of the match job to limit the number of organization sent to DnB.

I can run it manually and add a timestamp range for the Vendor Verification Date to pick up organizations recently matched , but this does not lend itself for having a scheduled job that runs once a day.

Thanks.