Feature Requests

UDF from Autotask is now an object, and can not be filtered by. How to filter by the fields in it?

Requirements: When I'm a client portal user, If I open a dashboard with the mapped comoany names slicer, I will only see my data If I'm and MSPbots Admin/tenant user, I should be able to see all client's data, and be able to select companies in the slicer when viewing the dashboard in MSPbots app If I use the dashboard/report for client-specific scheduled reporting, the receipient should receive the report with data filtered for their company As an MSPbots admin, I should be able to use one slicer for both functions, so that there's no need to create separate dashboards/reports for internal and client portal use

Can inactive names from QBO On-premise be filtered out for client mapping?

It would be helpful if there were some batch operations - we added a product mapping for Huntress (the product does not matter), but we only use it for one client. I must now edit EVERY client and mark it ignored. This process is VERY time consuming. How about some right click options right in the grid? We have some clients that don't do much with us and are not in any portal - how about an Ignore all option to automatically check each of the Ignore boxes. The filters at the top of the column don't appear to work. There should be three options per product, Ignored, Mapped and Not Mapped. When we view the list of Sources, there are two columns – the Mapped and Not Mapped. The Not Mapped is not clickable. Conversely, clicking the Not Mapped should show a window with the names from that Source that have not been mapped. This one is more important as we should be able to see data from that source that does not have a mapping in the system. This will help us to find errors in our datasets. I would expect the default sort order to be by Match status then client name - I would sort unmatched before the matched. This way attention is directed to the clients needing attention. In the left column, we click the Mapped numbers to quickly filter the matches. Why can’t we click on the No Mapped numbers to see what companies need fixing?

My expectation that the ultimate goal is the normalization of client names across products / datasets for simple reporting. For example, consider the following fictitious example: Webroot: Client Count CompanyOne 10 CompanyTwo 20 Sentinel One: Client Count Company-One 5 Company-Two 15 Mapping: ConnectWise Manage Webroot Sentinel One Company One CompanyOne Company-One Company Two CompanyTwo Company-Two Sample Report: Client Weboot Sentinel One Company One 10 5 Company Two 20 15 With this reporting dataset, slicers would work as long as the source of the names were the Manage clients. When I look at most of the datasets, I would expect to see the “native” client name and an alternate “Mapped” client name. For reporting purposes, we’d standardize on the mapped version.

We have a CSV export available out of Service Now which contains the company name and company code export. We were discussing possibly using this export to use as the primary data source of company mappings.