Synchronizing new CMDB attributes to MID servers?

[Marek Meres]

Hello All,

Do you know if there is a need / a way to synchronize new custom CMDB attributes to MID servers before they can be populated by custom Patterns?

Here is the situation I faced: I developed a new Pattern Extension to populate new custom attribute. It worked fine on DEV but when I promoted to TEST and (just in case) synced the patterns to MID servers the Pattern was shown in the log collecting the values and populating the payload (while in the extension) but then back in the main pattern log, the "Create CI" step showed payload without the new attribute. Finally I restarted all MID servers in the Discovery cluster and it did the trick but I really miss any documentation on that. 

Do you know if this feature is documented? ServiceNow simply answered that custom patterns are not supported normally...

[Community Alums]

Hi @Marek Meres , 

After reading your scenario, just few things to check 

1) did you capture that new attribute in an update set to test instance?  Please make sure type of attribute is appropriate. Is it a date field or string field. Depending on the type of data you want to populate select accurate type of attribute. 

2) how extension step captured and moved into test instance is an important step. Please make sure you are in the global scope. Most of the pattern extension are in global scope. 

please check out this post in the community related to extension step. 

https://www.servicenow.com/community/itom-articles/extending-patterns/ta-p/2326816

3) are you using transform table option in the extension step to sync up this data to the base table. That’s an important step. Please find below link and check step 7 and 8 in the screenshot. 

https://checksumfailed.com/blog/discoverypatternextentions/

If this solution resolved your issue, please mark it as helpful or accept it as the solution.

Regards, 

srinija 

[Marek Meres · Accepted solution]

Hi Srinija,

As mentioned, the situation was finally rectified by restarting all MID servers. So everything was properly captured and promoted up to the TEST instance.

Meanwhile ServiceNow confirmed there is no specific procedure for synchronizing custom attributes to the MID servers and our TEST instance behaviour must have been some glitch, which seems true, as promoting the custom attribute and pattern extension to the next instance (UAT) was smooth and everything worked immediately after promotion, not needing MID Server restarts.

Posting this if someone had similar problems then.

[Community Alums]

@Marek Meres , 

Glad the issue got resolved after restarting the MID Server. There is a ootb option to sync pattern to the MID Servers. please find the link, incase if that's helpful. 

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0745146

Regards, 

Srinija