Skip to content

Cross-source questions

Salesforce and NetSuite in one question

Ask questions that join Salesforce opportunities with NetSuite invoices and receivables, with the query and lineage for each system in the answer.

Short answer

One question can span Salesforce and NetSuite, such as which closed-won opportunities have no NetSuite invoice yet. Nexatron queries each within the asking person’s access, combines the results in an isolated step inside your workspace, and shows each source’s query. Salesforce and NetSuite are both available.

Example joined questions

Questions to ask. Each needs data from both systems; the answer depends on your own data and definitions.

  • Which opportunities closed won last quarter have no matching NetSuite invoice yet?
  • How does closed-won amount by account compare with invoiced amount in NetSuite for the same quarter, in each currency?
  • Which accounts with an open renewal opportunity have NetSuite receivables more than 60 days past due?
  • Which NetSuite customers were invoiced this year but have no Salesforce account owner?

Agree how a Salesforce account relates to a NetSuite customer before joining. Most teams keep a shared external ID on one side; matching by company name is a guess.

Check before you trust a joined answer

  • Several invoices and several opportunity line items can create a many-to-many join. Aggregate each side to a compatible grain first.
  • Booking, invoicing and cash are different events with different dates. Name the one the question means.
  • Salesforce sharing rules and the person’s NetSuite role both apply, so two people can get different, correct answers.

How a cross-source answer works

  1. Each system is queried within the person’s access

    Nexatron sends each part of the question to the system that holds it. A system each person signs in to answers as the person asking, and a shared connection reads the same data for everyone enabled on it.

  2. Results are joined inside your workspace

    Nexatron combines each system’s results in an isolated step inside your tenant when the question is asked. Nothing has to be consolidated into a warehouse first, and there is no pipeline to build.

  3. The queries come back with the answer

    The answer carries the generated query for each system and how many records matched, so a reviewer can check which system supplied which figure and repeat the check later.

  4. Joins follow links found at setup

    Nexatron joins on the links setup found between the systems, and says how many records matched. If no record matches, it says so and marks the figures as uncertain.

  5. Currencies are never added up as they are

    Amounts in different currencies are converted with one system’s own exchange rates where a usable rate source exists, and otherwise shown side by side with the reason.

  6. Longer than a single-source answer

    These answers take longer than single-source ones.

More on how it works and its limits: Cross-source analytics and the guide to cross-source analytics without a warehouse migration.