Currently we can only map sites in N-Central to the root account in Autotask. We should be able to map sites to Autotask locations.
similar to how you configure ConnectWise PSA Integration. Currently we are unable to utilize PSA integration as AutoTask has asked us not to enable it - it will cause downtime of their service every time our server syncs due to it currently trying to sync all active leads/prospects/customers instead of just customers.
The current system of selecting the correct customers for ticketing profiles is quite a hassle. When you want to add only specific customers to the ticketing profile you have to press add multiple times, until you have all the customers for which you want to configure the profile. Next you have to select all the customers that don't need the ticketing profile and delete them. A checkbox construction would be much easier ...more »
Have the ability to configure and send notifications based on the last time an agent has communicated with the NCentral server. The purpose would be to review this on a monthly basis and connect with clients about devices that are offline to help keep NCentral more organized.
I know there are filters and dashboards that can be created, but the ability to generate a PSA ticket would also be nice.
I'd like the ability to use 1 probe with multiple discovery jobs where each job would import the discovered assets into a specific site in N-Central. This would help with having the assets show up in the correct site in CW configurations and ensure that technicians can quickly see all devices in a specific site without going through any additional steps. Currently discovery jobs want a probe per site in N-Central which ...more »
For each device in N-Central, OSInfo and OSType are written to the Notes field in the corresponding Autotask configuration item. I'd like the ability to disable this. We'd like to put our own notes for each device in Autotask, but N-Central overwrites them with each sync. The device notes field also syncs with ITGlue so those notes are overwritten as well.
PSA type of integration with Salesforce CRM.
Solarwinds themselves use Salesforce as a CRM.
Code that can be customized and would allow N-Central to communicate with the Salesforce.
ConnectWise introduced the ability to merge tickets back in July 2016. After trying to verify compatibility with N-Central at the time, we learnt that merged tickets were not supported through N-Central as the associated ticket numbers wouldn't track back correctly after the merge takes place. I assumed that this would mean N-central would talk to ConnectWise about it, but it looks like that never happened or talks halted ...more »
I feel really stupid having to request this, but SolarWinds won't do anything without it. Whilst patching our PSA recently and facing outages, we have found that depending on the type of PSA issue you are facing (eg connectivity, backend sql problem), the failure notice you receive from a ticket not being created/updated will always include details of the customer and notification recipient, but for some inexplicable ...more »
PSA Integration relies on direct, uninterrupted communication with the PSA solution. API may encounter a network time out and not retry sending the information.
Establish some kind of queuing logic much like a mail server that could queue the messages for retry.
Manually adding a customer / site allows for enabling the PSA integration, this option is missing from the API call.
Customers added with the API need to be manually enabled for PSA integration. Adding this option to the API call would save this unnecessary operation.
We use RMM and MSP Manager. There seems to be a lack of configuration for the integration to MSP Manager. I would like more options of what and how tickets get created. For example, we have our site and devices in RMM to monitor and test on our own Servers and Lab. I would like the option to exclude these from creating tickets in MSP Manager.