- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-13-2020 12:00 PM
We are currently using Discovery to manage our inventory. We have discovery schedules setup with an specific location that run every day for different IP addresses range. However, we are running into the issue that the Company field is not being populated for the CIs, therefore the assets created don't have a company either. When I run Discovery, the location is set up properly, but the company stays empty. I have tried different types of Business Rules, but nothing seems to work. We are not domain separated, which means all of our inventory is in the global domain.
Is there something that can set the Company of the record to be the company of the Location?
Thank you.
Solved! Go to Solution.
- Labels:
-
Enterprise Asset Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-13-2020 12:04 PM
Did you try a business rule that runs on insert and update IF the company is NULL? Then in the Set Actions set the company to the same as location.company? This shouldn't require scripting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2020 05:54 AM
Hello,
Thank you for your reply.
The Run As account is an admin account that has access to the company table.
Also, we are not hard coding the company, since we not only use discovery for one company. For testing purposes I hard coded the company in the Business Rule to see if the Business Rule was running at the proper time and it worked, it set the company to the one I had put in, the issue is when I change the action to set the company to "Location.company", it wipes out the company field of the records again and it goes back to empty. I made sure that the company is in the same global domain as the asset records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2020 11:44 AM
Hello, we discovered that the issue was in the MID Server account, and everything is fixed now. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-16-2022 07:33 AM
Hi Astrid,
We are experiencing the same issue on our discovery. Can you please clarify what the issue was?