Is there a join for that within a transaction sear...
# arm
k
Is there a join for that within a transaction search? I see it if I'm using a revenue element search, but according to the 3rd party software that's pulling this search I'm limited to using a transaction search which is causing me some trouble.
j
Are you saying that your BI tool will only accept a transaction saved search? I thought a saved search is a saved search. We've used DOMO and able to pull any saved search in using the internal ID of the search. I've experienced similar issues trying to get everything into one search. The issue is that the revenue element is 2 levels away from the transaction so a transaction saved search won't pull the element.
k
That's what they're claiming, but I have doubts. I was using a different search (Revenue Element Search) that was working okay, but when the 3rd party tool pulled it, there were data integrity issues (random transaction lines would be missing compared to when I pulled it straight from NS). It's after we opened up a ticket that they claimed that "custom searches are buggy" and to use a transaction search. That being said, I'm having similar issues with a transaction search which they say should work. It's pretty inconsistent and extremely frustrating.
And yeah, it being two records away does seem to be the issue. I was trying to see if I could source that field and add it as a custom item field on the revenue arrangement or even the source transaction, but it doesn't look like it.
j
How we solved for it was exporting two different saved searches, and did the join in our BI tool. I had little luck in creating a custom field sourced from another transaction, I did create a custom field populated with a summary saved search, but those results will not pull in a saved search. I used a workflow to populate a second custom field that stores value using the summary custom field as the source, but that is a lot of extra steps and not best for a field that needs constant updating.
k
why won’t you use Analytics for that.
j
@Karina not trying to hijack this thread but I posed the same argument at my company. I could create good datasets and pivots in NS Analytics but our data team was unable or unwilling to configure our BI tool to accept the data from Analytics. Plus the cost of the connector factored into the decision. They also pull in a lot of data from Salesforce and Service now to create the flashy graphs and dashboards to justify what we spent on our BI tool. It might be the same issue that Kyle is facing.