Business apps: Dynamics 365, Dynamics 365 Finance and Supply Chain, NetSuite and Gong
How to connect Microsoft Dynamics 365 (Dataverse), Microsoft Dynamics 365 Finance and Supply Chain, Oracle NetSuite and Gong.
Status: Available, except Dynamics 365 Finance and Supply Chain, which is in testing: it is built on Microsoft's published documentation but has not yet been run against a live Finance and Supply Chain environment. The others are built on each vendor's published API, and validated in your account during onboarding.
| Source | Kind | Reads | Changes | People sign in with |
|---|---|---|---|---|
| Microsoft Dynamics 365 | dynamics365 |
OData queries, tables and columns, records with related rows | Create and update one record at a time, after the person confirms (off unless an admin turns it on). No deletes. | Their own work or school account |
| Microsoft Dynamics 365 Finance and Supply Chain | dynamics365_fo |
OData queries over data entities (vendors, purchase orders, inventory and so on), records with related rows | None (read-only) | Their own work or school account |
| Oracle NetSuite | netsuite |
SuiteQL queries, record types, records with sublists | Create and update one record at a time, after the person confirms (off unless an admin turns it on). No deletes. | Their own NetSuite login and role |
| Gong | gong |
Calls, call details, transcripts, users, activity and interaction stats | None (read-only) | A Gong technical admin's login, company-wide (see Gong) |
As everywhere in SourceLace, queries are checked before anything is sent, results are held for at most 30 minutes and never written to a database (see How long things are kept), and sign-in tokens are encrypted and never shown. Gong transcripts are read only when someone asks for them.
The redirect URL for all four is:
https://mcp.sourcelace.ai/connect/callback
At a glance
| Connects through | Sign-in | Network | Status | First test question | |
|---|---|---|---|---|---|
| Microsoft Dynamics 365 | Dataverse Web API (OData v4) | Personal sign-in | Nothing to open | Available | "Show 5 accounts from dynamics365:prod." |
| Microsoft Dynamics 365 Finance and Supply Chain | OData service of the environment (/data) |
Personal sign-in | Nothing to open | In testing | "List 5 vendors from dynamics365_fo:prod." |
| Oracle NetSuite | NetSuite REST web services (SuiteQL and the REST record service) | Personal sign-in | Nothing to open | Available | "Show 5 active customers in netsuite:prod." |
| Gong | Gong API (version 2) | Shared account (company-wide) | Nothing to open | Available | "List Gong calls from the last 7 days." |
Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.
Microsoft Dynamics 365
Each person signs in with their own Microsoft work or school account. Dataverse then applies that person's security roles, business units and field security to everything SourceLace reads or changes.
Sign-in asks for <org_url>/user_impersonation (Dynamics CRM, delegated: "act as the signed-in person") and offline_access (stay connected). SourceLace uses its own Microsoft app, so there is nothing to register.
What your admin does in Microsoft
Once per tenant for approval, then once per person for access. About 10 minutes.
Who: a Microsoft Entra admin who may grant tenant-wide consent (Global Administrator, Cloud Application Administrator or Application Administrator); a Power Platform administrator (or a System Administrator of the environment) for users and security roles; a Microsoft 365 admin for licences.
- Copy the Environment URL. In the Power Platform admin center, Environments → your environment: copy Environment URL, such as
https://corvanta.crm4.dynamics.com. That is theorg_urloption. - Approve SourceLace once (Entra admin). Most organizations do not let people approve apps themselves, so the first person to connect sees Need admin approval. Connect once yourself and tick Consent on behalf of your organization, or afterwards open the Entra admin center → Enterprise applications → SourceLace → Permissions → Grant admin consent. The permission is Dynamics CRM, user_impersonation.
- Give each person a licence (Microsoft 365 admin). Microsoft 365 admin center → Users → Active users → the person → Licenses and apps: tick a Dynamics 365 licence (such as Dynamics 365 Sales), then Save changes.
- Add each person to the environment with a security role (Power Platform admin). If the environment has a security group, first add the person to that Entra group. Then, in the Power Platform admin center, Environments → your environment → Settings → Users + permissions → Users: the person must be listed and enabled (Add user if not). Select them, Manage security roles, tick a role such as Salesperson, and Save. Dynamics applies this role to everything SourceLace reads or changes.
- Conditional Access: if your organization's Conditional Access policies limit which apps people may use, allow SourceLace in them.
Check that it worked: one person clicks Connect, signs in with their work account and asks the first test question from At a glance. In the Entra admin center, Enterprise applications → SourceLace → Sign-in logs shows their sign-in.
Microsoft's own guides: Power Platform admin documentation (search for "Assign security roles to users") and Microsoft Entra documentation (search for "Grant tenant-wide admin consent").
Add the source (SourceLace admin)
Kind: Microsoft Dynamics 365 (dynamics365).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
org_url |
Web address | (required) | https://corvanta.crm.dynamics.com |
The environment's address (step 1). An address copied from the browser while Dynamics 365 is open also works: everything after .dynamics.com is removed for you. Regional environments use crm4, crm11 and so on. Only https://<name>.crm<n>.dynamics.com addresses are accepted. |
To allow changes, turn on Allow changes and list the tables by their entity set names as search_schema shows them, such as accounts, opportunities.
What people can do
search_schemalists the tables they can see;describe_object accountsshows columns, choice values, lookups and related lists.query(languageodata) takes an entity set name plus OData options$select,$filter,$top(1 to 5,000),$expandand$orderby, such asaccounts?$select=name,revenue&$filter=revenue gt 100000&$orderby=revenue desc&$top=20. Other options, functions, actions and batch calls are refused before anything is sent.- Choices and lookups also come back with their display text, in a column named
<column>_label. get_record accounts <id>reads one record (the id is a GUID), and can add related lists such ascontact_customer_accounts.- Changes:
propose_changeshows the current and new values. The update is sent with the record's version (ETag), so Dynamics refuses it if someone changed the record after the preview. Lookups are set with"<navigation property>@odata.bind": "/contacts(<id>)". Deleting is not offered.
Microsoft Dynamics 365 Finance and Supply Chain
The ERP side of Dynamics 365: finance, purchasing, inventory, warehouse and transport. It is not the same as the Dynamics 365 source above, which reads Dataverse (sales, service and the other CRM tables) and cannot see this data. Each person signs in with their own Microsoft work or school account, and Finance and Supply Chain applies that person's own security roles to everything SourceLace reads. Reads only: nothing can be created, changed or deleted through this source.
Sign-in asks for the environment's default permissions (<environment_url>/.default, which includes Microsoft Dynamics ERP, Access Dynamics AX data) and offline_access (stay connected). SourceLace uses its own Microsoft app, so there is nothing to register in Azure, but two administrators must allow it (below).
What your admin does in Microsoft Dynamics 365 Finance and Supply Chain
Twice per environment, then once per person. About 20 minutes.
Who: a Microsoft Entra admin who may grant tenant-wide consent (Global Administrator, Cloud Application Administrator or Application Administrator); a Finance and Supply Chain system administrator for the registered apps and users; and whoever manages licences in the Microsoft 365 admin center.
- Copy the environment address. Open Finance and Supply Chain in your browser and copy the start of the address, up to
.dynamics.com, such ashttps://corvanta.operations.dynamics.com. In Microsoft Dynamics Lifecycle Services it is the environment's Application URL. That is theenvironment_urloption. - Approve SourceLace once (Entra admin). Most organizations do not let people approve apps themselves, so the first person to connect sees Need admin approval. Connect once yourself and tick Consent on behalf of your organization, or afterwards open the Entra admin center → Enterprise applications → SourceLace → Permissions → Grant admin consent. The permission is Microsoft Dynamics ERP, Access Dynamics AX data.
- Register SourceLace in the environment (Finance and Supply Chain system administrator). In Finance and Supply Chain open System administration → Setup → Microsoft Entra applications, select New, and enter the Client ID SourceLace support gives you (SourceLace's Microsoft application ID), a Name such as
SourceLace, and a User ID (Microsoft's guide recommends a dedicated service account that has only the permissions the integration needs, rather than the Admin user). Save. Without this step the environment refuses every sign-in. - Give each person a licence and a user (admins). Each person needs a Dynamics 365 Finance or Supply Chain Management licence (Microsoft 365 admin center → Users → Active users → the person → Licenses and apps), and an enabled user in the environment with security roles (System administration → Users → Users). Finance and Supply Chain applies those roles to everything SourceLace reads.
- Conditional Access: if your organization's Conditional Access policies limit which apps people may use, allow SourceLace in them.
Check that it worked: one person clicks Connect, signs in with their work account and asks the first test question from At a glance. In the Entra admin center, Enterprise applications → SourceLace → Sign-in logs shows their sign-in.
Microsoft's own guides: Dynamics 365 Finance documentation (search for "Service endpoints overview" and "Open Data Protocol (OData)") and Microsoft Entra documentation (search for "Grant tenant-wide admin consent").
Add the source (SourceLace admin)
Kind: Microsoft Dynamics 365 Finance and Supply Chain (dynamics365_fo).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
environment_url |
Web address | (required) | https://corvanta.operations.dynamics.com |
The environment's address (step 1). An address copied from the browser while the app is open also works: everything after .dynamics.com is removed for you. Only https://...dynamics.com addresses are accepted. Do not use the Dataverse address (.crm.dynamics.com): that is the Dynamics 365 source above. |
What people can do
search_schemalists the data entities the environment makes public.describe_object VendorsV2shows the columns, read from one sample row (so an entity with no rows shows none).query(languageodata) takes a data entity name plus OData options$select,$filter,$top(1 to 10,000),$orderby,$expand(first level) andcross-company=true, such asVendorsV2?$select=VendorAccountNumber,VendorOrganizationName&$top=20&cross-company=true. Only the person's default company is read unlesscross-company=trueis added; then every company they may access is read, and$filter=dataAreaId eq 'usmf'picks one. Text matches use a wildcard (Name eq '*retail*');has,in, functions, actions and batch calls are refused.get_record VendorsV2 "dataAreaId='usmf',VendorAccountNumber='1001'"reads one record. Finance and Supply Chain needs every key field of the entity.
Oracle NetSuite
Each person signs in with their own NetSuite login and picks a role. NetSuite then applies that role's permissions and restrictions to every query and every change. Changes are off until a SourceLace admin turns them on (see Add the source).
What your admin does in NetSuite
Once per NetSuite account (a sandbox is a separate account: do it there too). About 15 minutes.
Who: a NetSuite Administrator.
- Turn on the features. Setup → Company → Enable Features → SuiteCloud tab. Under SuiteTalk (Web Services) tick REST Web Services; under Manage Authentication tick OAuth 2.0. Accept the SuiteCloud Terms of Service if NetSuite asks, then Save.
- Install SourceLace's integration. Setup → Integration → Manage Integrations → Install. Enter the Application ID that support@sourcelace.com gives you, and click Install. The integration SourceLace then shows State: Enabled, with Authorization Code Grant and the scope REST Web Services. Without this step, sign-in fails with "invalid client". The integration record's token settings decide how long people stay connected before they connect again.
- Give the role the permissions. Setup → Users/Roles → Manage Roles, Edit the role people use (or Customize a standard role, which saves a copy). On Permissions → Setup, add REST Web Services and Log in using OAuth 2.0 Access Tokens, both at level Full. On Permissions → Lists and Transactions, give at least View on the records people should see (and Create or Edit on the records they may change, if changes are on). Save. Without the two Setup permissions, NetSuite refuses every call with "Invalid login attempt".
- Give people that role. Lists → Employees → the person → Edit → Access tab: add the role under Roles, and Save. People should sign in with this everyday role: NetSuite may refuse OAuth 2.0 sign-in with the Administrator role.
- Copy the Account ID. Setup → Company → Company Information → Account ID, such as
1234567or1234567_SB1for a sandbox. That is theaccount_idoption.
Check that it worked: one person clicks Connect, signs in, picks the role from step 3 and asks the first test question from At a glance. In NetSuite, Setup → Users/Roles → View Login Audit Trail shows the OAuth 2.0 sign-in and, if NetSuite refused, the exact reason.
NetSuite's own guide: NetSuite documentation (search for "REST Web Services" and "OAuth 2.0").
Add the source (SourceLace admin)
Kind: Oracle NetSuite (netsuite).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
account_id |
Text | (required) | 1234567 or 1234567_SB1 |
From step 5. Sandboxes and release previews end in _SB1, _RP and so on. |
Sign-in asks for the scope rest_webservices.
To allow changes, turn on Allow changes and list the record types as search_schema shows them, such as customer, contact. Nothing new is needed in NetSuite: the sign-in already includes REST web services, so nobody needs to connect again.
What people can do
search_schemalists record types;describe_object salesordershows the fields and sublists.query(languagesql) takes one SuiteQLSELECT(orWITH ... SELECT), such asSELECT id, companyname, email FROM customer WHERE isinactive = 'F'. All transactions are in thetransactiontable, with atypecolumn such as'SalesOrd'. Anything that could change data,SELECT ... INTOand more than one statement are refused before NetSuite is called. Statements can be up to 20,000 characters; noLIMITis needed, since SourceLace pages through results itself.get_record salesorder 42reads one record by its internal id (digits only); additem(or another sublist) to get its lines, up to 50 per sublist.- Changes (when an admin has turned them on for that record type):
propose_changeshows a preview (for an update, each field's current value next to the new one), andapply_changemakes the change after the person confirms. A create returns the new record's internal id.- Only a record's own fields can be set: text, numbers, true/false, or another record's internal id for a reference field (such as
subsidiary: 1). Sublists (such as a sales order's lines) and subrecords (such as addresses) are not changed. Unknown fields and fields NetSuite sets itself are refused in the preview, before anything is written. - The person's NetSuite role decides what is allowed. If the role cannot change that record, NetSuite's own message comes back.
- If someone changed the record between the preview and the confirmation, the change is not made and the person is asked to preview it again.
- Deletes are refused. NetSuite records are usually made inactive rather than deleted: update the record's
isInactivefield totruewhere the record type has one.
- Only a record's own fields can be set: text, numbers, true/false, or another record's internal id for a reference field (such as
Gong
Gong is read-only: calls, call details (participants, Gong's brief, key points, topics, trackers and linked CRM records), transcripts, users, and activity and interaction stats.
Important: Gong's access is company-wide, not per person. Gong lets only its technical administrators authorize an app, and the sign-in gives access to the whole company's Gong data; Gong does not apply each person's own Gong permissions to API calls. So:
- Add a Gong source only where everyone who can use it may see all calls and transcripts. Narrow who can use it with access by group.
- The person who connects must be a Gong technical admin.
- Gong does not always say which user signed in, so the audit trail may name the Gong company (
gong:<api address>) instead of a person.
Sign-in asks for api:calls:read:basic, api:calls:read:extensive, api:calls:read:transcript, api:users:read, api:stats:interaction and api:stats:user-actions. SourceLace has its own Gong app, so there is nothing to register.
Each Gong company has its own API address (such as https://us-12345.api.gong.io). Gong sends it with the sign-in, and SourceLace only ever calls that address (it must end in .gong.io).
What your admin does in Gong
Once. About 5 minutes.
Who: a Gong technical administrator. Gong refuses the app for anyone else.
- Check you are a technical administrator. In Gong, Company settings → Team members (or Permission profiles): your permission profile must have Technical administrator ticked. If not, a Gong admin ticks it for you, or connects instead.
- Connect. After your SourceLace admin adds the source, click Connect on it. Gong lists the six permissions above: approve every one. A sign-in with some left out fails later with "Gong refused this (HTTP 403)".
- Optional: pin the Gong company. In Gong, Company settings → Ecosystem → API shows your company's API address, such as
https://us-12345.api.gong.io. Give it to your SourceLace admin for theapi_baseoption, so a sign-in to another Gong company is refused.
Check that it worked: ask the first test question from At a glance. To remove SourceLace later, revoke it in Gong under Company settings → Ecosystem → API.
Gong's own guide: Gong help center (search for "Technical administrator" and "API").
Add the source (SourceLace admin)
Kind: Gong (gong).
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
api_base |
Web address | (none: taken from the sign-in) | https://us-12345.api.gong.io |
Optional. Pins the source to one Gong company (step 3): a sign-in to any other company is refused. |
What people can do
query (language gong_json) takes one small JSON object:
| Object | Example | Notes |
|---|---|---|
calls |
{"object": "calls", "from": "2026-09-01", "to": "2026-10-01", "details": true} |
from and to default to the last 30 days (at most a year). Filter with call_ids, user_ids (the call's host) or workspace_id. details adds participants, brief, key points, topics and trackers. |
transcripts |
{"object": "transcripts", "call_ids": ["7782342274025937895"]} |
Up to 20 calls. One row per stretch of speech, with the speaker's name. |
users |
{"object": "users"} |
Everyone in the Gong company. |
activity_stats |
{"object": "activity_stats", "from": "2026-09-01"} |
Calls hosted, attended, feedback and scorecards, per user. |
interaction_stats |
{"object": "interaction_stats", "user_ids": ["234599484848423"]} |
Talk ratio, longest monologue, interactivity, patience, question rate, per user. |
Ids are given as text. get_record calls <id> reads one call with its details and linked CRM records, and adds the transcript when transcript is asked for as a related list. Gong allows about 3 calls a second; when it asks SourceLace to slow down, SourceLace waits and tries again twice.
When something goes wrong
Each system has its own table: Dynamics 365, Dynamics 365 Finance and Supply Chain, NetSuite and Gong. For all of them, "The dynamics365 connector is not available yet." (or dynamics365_fo, netsuite, gong) means SourceLace's app for that system is not set up on this server yet: contact support.
When something goes wrong with Dynamics 365
| What you see | What it means | What to do |
|---|---|---|
| "Sign-in was not completed: AADSTS65001 ... Your Microsoft Entra admin approves SourceLace once ..." (or AADSTS90094, "Need admin approval") | Your tenant does not let people approve apps, and no admin has approved SourceLace yet. | An Entra admin grants admin consent (step 2). |
| "Microsoft sign-in failed: AADSTS500011 ..." | Microsoft cannot find Dynamics 365 at org_url in your tenant. |
Copy the Environment URL again (step 1). |
| "Microsoft sign-in failed: AADSTS50020 ..." | The person signed in with an account from another organization. | Sign in with a work account of the organization that owns the environment. |
| "Microsoft sign-in failed: AADSTS53003 ..." | A Conditional Access policy blocked the sign-in. | Allow SourceLace in the policy (step 5). |
| "Microsoft sign-in failed: ..." (another code) | Microsoft's own reason follows. | Check steps 1 and 2. |
| "You signed in to Microsoft, but you are not a user of this Dynamics 365 environment, or you have no security role in it ..." | The person is not an enabled user of the environment, is not in its security group, or has no security role. | Add them and give them a role (steps 3 and 4). |
| "Dynamics 365 did not accept your new sign-in. Check that the source's org_url is this environment's Environment URL ..." | The sign-in was for another environment. | Copy the Environment URL again (step 1). |
| "... has no org_url. An admin sets it to the environment's address ..." or "The org_url for ... must be a Dynamics 365 address such as https://corvanta.crm4.dynamics.com ..." | org_url is empty or not a Dynamics 365 address. |
Copy the Environment URL (step 1). |
| "Dynamics 365: Principal user ... is missing prv... privilege ..." | The person's security role lacks that table or action. | Give a role that includes it (step 4). |
| "Dynamics 365 has no table '...' that you can see. Use search_schema to find one." | Not an entity set name (accounts, not account), or the role does not include that table. |
Use the name search_schema shows. |
| "'...' is not allowed. Use only $select, $filter, $top, $expand, $orderby." | Another OData option was used. | Remove it. |
| "This record changed in Dynamics 365 after the preview. Propose the change again." | Someone changed the record after the preview. | Ask for a new preview. |
| "Dynamics 365 accepts create and update through SourceLace, not delete." | Deletes are not offered. | Delete in Dynamics 365 itself. |
| "Dynamics 365: not found, or you cannot see it." | The id is wrong, or the role does not allow it. | Check the id and the person's role. |
| "Dynamics 365 is limiting how fast SourceLace can call it. Wait a few seconds and try again." | Dataverse's service limits. | Wait and ask again. |
| "Your Dynamics 365 sign-in has expired." | The sign-in ended. | Connect again. |
| "SourceLace's Microsoft sign-in is not set up correctly." | SourceLace's own Microsoft app is not configured properly on SourceLace's side. | Contact support. |
| "A Dynamics 365 query is an entity set name with OData options, such as accounts?$select=name&$top=10." | The query is not in that form: navigation paths, functions and actions are not accepted. | Use $expand for related rows. |
| "The query has characters that are not allowed (line breaks, # or an address)." or "... needs a value, such as ...=..." | The query has a line break, a #, a full web address, or an option with nothing after it. |
Write it on one line as an entity set name with options such as $top=10. |
| "$top must be a whole number from 1 to ...." | The row count is not a whole number or is above the limit. | Use a whole number up to the limit named. |
| "Dynamics 365 sent a next page at an unexpected address." or "SourceLace refused to make that call to Dynamics 365." | Dynamics' answer pointed outside your environment, which SourceLace never follows. | Try again. If it repeats, contact support. |
Finance and Supply Chain in one question across systems
A data entity (such as VendorsV2) can be a table in one question across your systems, so an AI app can put vendor balances next to your CRM accounts or your data warehouse in a single answer. Name the table as "dynamics365_fo:prod"."VendorsV2" and ask for the fields you need. Three things to know:
- Every company the person can reach is read, not only their default company. The entity's own
dataAreaIdcolumn says which company a row belongs to, so a question can ask for one ("dataAreaId" = 'usmf'). The person's own security roles still decide what they can read. - Numbers, yes/no fields and the company are asked of Finance and Supply Chain; other conditions are applied by SourceLace after the rows arrive, so a filter on a name, a code or a date does not make a large read smaller.
- A very large entity is read only up to a limit. When SourceLace stops at the limit, the answer says it is incomplete and says why, instead of looking whole.
When something goes wrong with Dynamics 365 Finance and Supply Chain
| What you see | What it means | What to do |
|---|---|---|
| "Need admin approval" on the Microsoft sign-in page, or "Microsoft sign-in failed: AADSTS65001 ..." | Your Entra admin has not approved SourceLace's Microsoft Dynamics ERP permission yet. | Step 2. |
| "Microsoft sign-in failed: AADSTS500011 ..." or "AADSTS650057 ..." | Microsoft cannot find Finance and Supply Chain at environment_url in your tenant, or SourceLace's app does not have the Dynamics ERP permission. |
Copy the address again (step 1); then ask SourceLace support to confirm the app's permissions. |
| "Dynamics 365 Finance and Supply Chain did not accept your new sign-in. Check that the source's environment_url is this environment's address ..." | The environment refused a token it was just given: wrong address, SourceLace not registered in Microsoft Entra applications, or the person is not an enabled user. | Steps 1, 3 and 4. |
| "... has no environment_url. An admin sets it to the address the environment is opened at ..." or "The environment_url for ... must be a Dynamics 365 Finance and Supply Chain address ..." | environment_url is empty or not a dynamics.com address. |
Copy the address (step 1). |
| "Dynamics 365 Finance and Supply Chain: your user is not allowed to read this. Ask your finance and operations administrator for a security role that can." | The person's security roles do not include that data. | Give a role that does (step 4). |
| "Dynamics 365 Finance and Supply Chain: not found, or you cannot see it." | The entity or key does not exist, is not public, or the roles do not allow it. | Use search_schema for the entity name; give every key field for get_record. |
| "Dynamics 365 Finance and Supply Chain is limiting how fast SourceLace can call it. Wait a few seconds and try again." | The environment's service protection limits (HTTP 429). | Wait and ask again; ask fewer rows at a time. |
| "... sent a next page at an unexpected address." | The environment answered with a page address that is not its own; SourceLace stopped. | Contact support. |
| "A Dynamics 365 Finance and Supply Chain query is a data entity name with OData options ..." or "'...' is not allowed. Use only ..." | The query uses something other than the allowed options. | Rewrite it with $select, $filter, $top, $orderby, $expand or cross-company=true. |
| "Your Dynamics 365 Finance and Supply Chain sign-in has expired." | The sign-in ended. | Connect again. |
| "The query has characters that are not allowed (line breaks, # or an address)." or "... needs a value, such as ...=..." | The query has a line break, a #, a full web address, or an option with nothing after it. |
Write it on one line as a data entity name with options such as $top=10. |
| "cross-company can only be true, as in cross-company=true." | The cross-company option was given another value. | Write cross-company=true, or leave it out to read only the default company. |
| "SourceLace refused to make that call to Dynamics 365 Finance and Supply Chain." | The call was to an address outside your environment, which SourceLace never makes. | Try again. If it repeats, contact support. |
When something goes wrong with NetSuite
| What you see | What it means | What to do |
|---|---|---|
| "NetSuite sign-in failed: invalid_client ..." | SourceLace's integration is not installed in this account (or the sandbox). | Install it (step 2). |
| "Sign-in was not completed: ..." or "NetSuite sign-in failed: ..." (another reason) | NetSuite refused on its sign-in page, often because the role lacks Log in using OAuth 2.0 Access Tokens, or the person chose the Administrator role. | Check the role's permissions (step 3), and sign in with the everyday role. |
| "NetSuite refused your sign-in for this role (Invalid login attempt), so connecting again will not help ..." | The role lacks REST Web Services or Log in using OAuth 2.0 Access Tokens, or the features are off. | Steps 1 and 3. The Login Audit Trail shows the exact reason. |
| "... has no account_id. An admin sets it to the NetSuite account id ..." or "The NetSuite account_id for ... must look like 1234567 or 1234567_SB1." | account_id is empty or malformed. |
Copy the Account ID (step 5). |
| "NetSuite did not say which user signed in." | NetSuite's token did not name the user. | Contact support. |
| "SELECT ... INTO is not allowed in a read-only query." | Only plain reads are allowed. | Use a plain SELECT. |
| "NetSuite: not found, or you cannot see it." | The record type or id is wrong, or the role does not allow it. | Check them, and the role's permissions (step 3). |
| "NetSuite: your NetSuite role does not allow this. ..." | The role lacks view, create or edit access to that record type. | Add it to the role (step 3). |
| "NetSuite: ..." (another message) | NetSuite's own words, such as an unknown field in a SuiteQL query. | The AI usually fixes the query itself. |
| "NetSuite is limiting how many calls SourceLace can make at once. Wait a moment and try again." | NetSuite's limit on calls at once for the account. | Wait and ask again. |
| "... has no field '...'. Use describe_object to see them." or "... is set by NetSuite and cannot be changed." | The change names a field that does not exist, or one NetSuite fills in itself. | Use the field names describe_object lists. |
| "... is a sublist; SourceLace changes a record's own fields only." (or subrecord) | Lines and addresses are not changed. | Change them in NetSuite itself. |
| "This ... record changed in NetSuite after the preview. Propose the change again." | Someone changed the record after the preview. | Ask for a new preview. |
| "SourceLace does not delete NetSuite records. ..." | Deletes are refused. | Set isInactive to true instead. |
| "Your NetSuite sign-in has expired." | The sign-in ended after the integration's token period. | Connect again. |
| "SourceLace refused to make that call to NetSuite." | The call was to an address outside your NetSuite account, which SourceLace never makes. | Try again. If it repeats, check the Account ID and contact support. |
When something goes wrong with Gong
| What you see | What it means | What to do |
|---|---|---|
| "Sign-in was not completed: ..." | Gong refused on its sign-in page, usually because the person is not a technical administrator. | A technical administrator connects (step 1). |
| "Gong sign-in failed: ..." | Gong's own reason follows, such as an expired sign-in code. | Connect again. |
| "Gong refused this (HTTP 403). Gong's API works only when a Gong technical administrator connected and approved every permission ..." | The person who connected is not a technical administrator, or left a permission out. | A technical administrator connects again and approves every permission (step 2). |
| "You signed in to a different Gong company than ... uses. Connect again with the right Gong account." | The sign-in was for another Gong company than api_base. |
Sign in to the Gong company named in api_base. |
| "The Gong api_base for ... must be Gong's API address, such as https://us-12345.api.gong.io." | api_base is not a Gong API address. |
Copy it (step 3), or clear it. |
| "Gong did not give a valid API address for your company." or "SourceLace does not know your Gong company's API address yet." | Gong's sign-in answer had no usable API address. | Connect again. If it repeats, set api_base (step 3). |
| "'...' is not a Gong object. Use calls, transcripts, users, activity_stats, interaction_stats." | The query named another object. | Use one of those objects. |
| "Gong: no call with id ..." | The call does not exist. | Check the id with a calls query. |
| "Gong is limiting how fast SourceLace can call it. Wait a few seconds and try again." | Gong allows about 3 calls a second. | Wait and ask again. |
| "Gong: ..." (another message) | Gong's own words, such as a date range it does not accept. | The AI usually fixes the query itself. |
| "Your Gong sign-in has expired." | The sign-in ended, or SourceLace was revoked in Gong. | A technical administrator connects again. |
| "SourceLace refused to make that call to Gong." | The call was to an address outside Gong, which SourceLace never makes. | Try again. If it repeats, check the source's API address and contact support. |