Use this guide if you manage a Cademy course provider account and want to send its training records to NetSuite. Complete the NetSuite preparation with your NetSuite administrator, then connect and configure the app in Cademy.
A record is one saved item, such as a contact. A field is one detail on it, such as an email address. A connection links Cademy to one NetSuite account. A module is the group of records you want to send. A field mapping matches a Cademy field to a NetSuite field.
What the integration sends
The integration sends data from Cademy to NetSuite. It does not bring changes made in NetSuite back into Cademy.
Contacts: sends a contact when it is created or updated in Cademy. You can include fields from its linked Organisation.
Occurrences: sends individual course dates when they are created or updated. “Occurrence” means a course date in this integration. You can include fields from the course. For a block of sessions, Cademy sends the individual session dates, not the overall block record.
Certificates: sends mapped certificate information when a certificate is issued. You can include information from its contact, course, course date, Registration (the person’s place on a course) and Order (the purchase record). This creates or updates a NetSuite record; it does not upload the certificate PDF.
Connecting, enabling a module or saving mappings does not import all existing records. There is no bulk historical sync button. After setup, new or changed contacts and course dates can sync. Certificates are sent when issued; existing certificates are not sent just because you connect the app.
Organisation, course, Registration and Order fields can supply values to the modules above. They are not separate NetSuite sync modules. Changes to those related records alone do not trigger an update to an already-synced contact, course date or certificate.
Before you start
You need access to your provider’s Cademy admin dashboard, with the NetSuite app enabled for the account. Custom plans include it by default; Free, Starter, Pro and Teams do not. The app card uses the plan label Enterprise and shows Beta.
Your NetSuite administrator completes “Prepare NetSuite” below. A NetSuite role controls which records a user can see and change. The administrator must prepare an active user and a role for this connection before you enter the connection details in Cademy.
Agree these details before you start:
Which NetSuite account to use: the live account or a sandbox, which is a separate test account.
Where contacts, course dates and certificates will be saved in NetSuite. The record type is the kind of item you will create. Custom record types and their required fields must already exist; Cademy does not create them.
Which fields must be filled in, and which fields link to another NetSuite record or list. These links use an internal ID, the number NetSuite uses to identify an item.
The NetSuite page or saved list you will use to check each result. Get the exact page for each custom record type from your NetSuite administrator.
Once the administrator has prepared NetSuite, continue at “Connect the app in Cademy”.
This Cademy connection uses token-based authentication (TBA). You enter integration and access-token credentials, not your NetSuite login password. Oracle states that NetSuite 2027.1 will prevent creation of new TBA integrations while existing integrations continue working. This guide describes the current TBA connection, not an OAuth 2.0 setup. See Oracle's TBA integration guidance.
Prepare NetSuite
1. Enable the required features
Ask your NetSuite administrator to complete these steps in the account you will connect.
Open Setup > Company > Setup Tasks > Enable Features.
Open SuiteCloud. Under SuiteTalk (Web Services), enable REST Web Services. Enable Token-based Authentication under the authentication features.
Open Analytics and enable SuiteAnalytics Workbook.
Review and accept any required NetSuite terms, then select Save.
These are NetSuite settings. Installing the Cademy app does not enable them. See Oracle's REST prerequisites and authentication features.
2. Create or open the integration role
These steps are for your NetSuite administrator. Use a role dedicated to this connection, such as “Cademy Sync”.
If the role already exists, open Setup > Users/Roles > User Management > Manage Roles and select Edit beside that custom role.
For a new role, open Setup > Users/Roles > Manage Roles > New. Enter “Cademy Sync” in Name. Select the Center Type appropriate to your integration user; this sets the starting permissions. Your NetSuite administrator should choose this for your account.
Review those starting permissions, then add the permissions in the next section before saving.
Customize beside a standard role creates a copy with that role’s permissions. It is an alternative to creating a new role, not the same action as editing your existing Cademy role. See Oracle’s role creation guide.
3. Set the role’s permissions
On the role you opened or created:
Open Permissions > Setup. Select REST Web Services, set Level to Full, then select Add.
Still under Setup, select Log in using Access Tokens, set Level to Full, then select Add.
Open Permissions > Reports. Select SuiteAnalytics Workbook, set Level to Edit, then select Add.
Open Permissions > Lists. Select Contacts, set Level to Edit, then select Add. This level allows viewing, creating and updating contacts.
Give the role access to any other records and lists used by your mappings. The required permissions depend on the fields you choose. Check the role’s account restrictions, including subsidiaries if your account uses them.
Select Save.
The REST permissions let Cademy connect. Record permissions let it read and write the actual data. A successful connection test does not prove that all record permissions are correct. See Oracle’s REST setup, permission settings and access levels.
For each custom training or certificate record type:
Open Customization > Lists, Records, & Fields > Record Types and open the required type.
Check Access Type. If it is Use Permission List, open Permissions. In Role, select the same integration role, such as “Cademy Sync”. Set Level to Edit.
Check Restrict. The role must be able to read and update the records Cademy will use; restrictions to records created by that user can block updates to existing records. Keep any form or search restrictions appropriate to your account.
Select Add, then Save. Repeat for the other custom record types you will sync.
If the type uses a different Access Type, your administrator must apply its existing permission model. Do not change that model just to follow the permission-list example. Oracle explains the different permission models and the full permission-list steps.
4. Assign the role to a NetSuite user
Use an active NetSuite employee user approved for this connection. If a new employee record is needed, the administrator can create it at Lists > Employees > Employees > New, complete the account’s required details and select Save. Follow Oracle’s employee setup guide.
Open Lists > Employees > Employees, then select Edit beside the user.
Open Access and check that Give Access is enabled. For a user who does not yet have access, complete Oracle’s access setup, including their email and sign-in setup.
Under Roles, select the Cademy integration role in Role, then select Add.
Select Save.
The person who creates the access token in step 6 needs Access Token Management. The integration role uses Log in using Access Tokens. These are different permissions. Your administrator can create the token; the integration user does not need permission to manage everyone’s tokens.
5. Create the integration credentials
Open Setup > Integration > Manage Integrations > New.
Enter a Name, such as “Cademy”, and keep State set to Enabled.
On Authentication, enable Token-based Authentication (TBA). You will create the token in step 6; no Cademy callback URL is needed.
Select Save. Store the displayed Consumer Key and Consumer Secret securely before leaving the page.
These identify the Cademy integration in NetSuite. They are different from the Token ID and Token Secret created next. NetSuite only displays the secrets when they are generated; if you reset these keys in NetSuite, the old keys stop working.
6. Create the access token
Using a role with Access Token Management, open Setup > Users/Roles > User Management > Access Tokens.
Select New Access Token.
Choose the Cademy integration in Application Name, your integration user in User, and its integration role in Role.
Enter a recognisable Token Name, then select Save.
Store the displayed Token ID and Token Secret securely before leaving the confirmation page.
These credentials belong to that application, user, role and account. If you lose the token credentials, create a new token. Do not send credentials by email or include them in screenshots. See Oracle's token setup guide.
7. Find the account ID
Open Setup > Company > Company Information and copy Account ID. Use this exact account identifier for both Account ID and Realm in Cademy. For example, a fictional sandbox account could be 1234567_SB1. Preserve its sandbox suffix and underscore; do not paste a browser URL into either field.
Sandbox tokens must be created in that sandbox. Production tokens are not copied there, and a sandbox refresh requires new sandbox tokens. See Oracle's account ID guidance and TBA account guidance.
Connect the app in Cademy
Sign in to the Cademy admin dashboard and select the provider account you want to connect.
Open Apps, select NetSuite, then select Install. If the app is installed already, open NetSuite to see its connections.
Select + Add Connection. If there are no connections, Connect your first NetSuite account opens the same setup.
In Credentials, complete the fields below in the order shown.
Select Test & continue. When the test succeeds, Verify displays NetSuite connection succeeded.
Select Save connection, then Finish on Done. The connection appears with the status Ready.
The connection fields are:
Account Name: an optional name to help you identify this connection, for example “Production NetSuite”.
Account ID: the identifier copied from NetSuite's Company Information page.
Realm: the same NetSuite account identifier.
Consumer Key: the key from the integration record.
Consumer Secret: the secret paired with that Consumer Key.
Token ID: the access token created for the integration user and role.
Token Secret: the secret paired with that Token ID.
Open Advanced only to inspect or change these additional settings:
Signature Method: keep HMAC-SHA256. Although the selector also shows HMAC-SHA1, Oracle no longer supports that method.
REST Base URL: leave blank so Cademy builds the address from your Account ID. Enter a different address only if your NetSuite administrator supplies it. It must be the account’s HTTPS SuiteTalk API address, without login details or a custom port.
Metadata URL: leave blank so Cademy chooses the address automatically. Enter a different address only if your NetSuite administrator supplies it for this account.
The test checks whether Cademy can read the list of Contact fields in NetSuite. It does not create a record or check every permission and mapping. Finish the module setup and check actual sync results before relying on the connection. See Oracle's signature-method guidance.
Set up field mappings
Open Apps > NetSuite, select your connection card, then open Mappings. The modules appear in this order: Contacts, Occurrences, Certificates.
Configure each module you need. Before you save any settings, Contacts has its switch on; Occurrences and Certificates start disabled. Enabled beside Not set up does not mean records are already syncing.
Open the module, for example Contacts.
Turn on the switch beside Contacts Sync, Occurrences Sync or Certificates Sync, as appropriate.
Open the list that chooses where records will be saved: Map to NetSuite contact, Map to NetSuite job or Map to NetSuite document.
Select the record type agreed with your NetSuite administrator. For Contacts, use the standard Contact type. If your agreed course-date or certificate type is not listed, select Load All NetSuite Modules, then search for and select it.
Under Field Mappings, select Add Mapping.
Select the Cademy Module, then the Cademy Field. Choose its matching field under NetSuite contact Field, NetSuite job Field or NetSuite document Field, depending on the module. Add Mapping may select a Cademy field for you; check that it is the one you want.
Repeat for the fields you need, including all fields required by your NetSuite record type. Configure reference values using the next section when required.
Select Save at the top. Confirm the message Contacts mappings saved, Occurrences mappings saved or Certificates mappings saved. Reopen Mappings to check the module's state and saved field count.
The initial destination choices are Contact (contact), Training Class (customrecord_training_class) and Certificate (customrecord_cert_track), respectively. The latter two are suggested custom record types, not records installed by Cademy. Choose the actual record type in your NetSuite account. If you need to define a custom type first, your NetSuite administrator can use Customization > Lists, Records, & Fields > Record Types > New and follow Creating a New Custom Record Type. Its fields and required values depend on your organisation’s NetSuite setup. A type appearing in the list does not mean it is suitable for every module.
The source choices depend on the module:
Contacts: Contacts, Organisations.
Occurrences: Occurrences, Courses.
Certificates: Certificates, Contacts, Courses, Occurrences, Registrations, Orders.
Each Cademy field can be selected once within a module. If it is missing from another row’s list, edit the row where it is already selected. Use a different NetSuite field for each value you want to keep.
For a simple example, if your Cademy contact’s email field is named Email, select Contacts as the Cademy Module and Email as the Cademy Field. Under NetSuite contact Field, choose the email field with ID email, then select Save. Field names may differ in your account; the ID shown beside the NetSuite field helps you identify it. Check the saved row, then use the first-sync steps below to confirm the email appears on the NetSuite contact.
Only choose fields that have data for the records you intend to sync. A certificate without a related Order cannot supply Order values. Fields that hold several selected answers, such as checkbox or multi-select fields, are not sent by this integration, even if the editor lets you select them. NetSuite fields shown as unavailable also cannot be mapped.
For Contacts, Cademy also supplies available email, first name, last name and a contact name/identifier when those target values have not been set by mappings. Contacts matches an existing NetSuite record by email before creating one on its first sync; subsequent updates use the saved NetSuite record ID. Review duplicate email addresses before enabling contact sync because an email match can update an existing NetSuite record.
Occurrences and Certificates require at least one saved field mapping. Cademy keeps the link to the NetSuite record so later syncs update the same record.
Match dropdown values to NetSuite references
Use Map values when a Cademy custom dropdown or radio field needs to select a NetSuite reference (a field that links to another NetSuite item). Matching names alone is not enough: NetSuite needs the option’s internal ID.
From Apps > NetSuite > your connection > Mappings, open the relevant module and find the mapping row.
Select Map values beside its NetSuite reference field.
In Map values for …, check the Cademy field and NetSuite list.
For each Cademy value, choose the matching NetSuite option. Add Cademy Value adds another choice you can fill in.
To copy choices from NetSuite, select Add from NetSuite, tick the choices you need, then select Add 1 as Cademy value or Add [number] as Cademy values. The button’s number matches your selection. The choices then appear in the mapping window.
Use All, Mapped and Unmapped to check the pairs. Use Previous and Next if there is more than one page.
Select Save changes in the window, then Save on the module page.
For example, a fictional Cademy dropdown value “Edinburgh” can map to a NetSuite location labelled “Edinburgh Office”, with internal ID 42. The integration sends the ID, not the Cademy label. Return to the same mapping's Map values window to confirm the saved pair.
Map every choice you use, including choices added later. If a choice has no saved match, Cademy sends its original value as the NetSuite ID. NetSuite can reject it if it is not a valid ID.
Save changes also updates the options on the selected Cademy custom dropdown or radio field. Adding or removing values here changes that field's choices wherever it is used in Cademy. Review the whole list before saving; the module's later Save is still required to save the integration mapping.
If NetSuite has not identified the reference list, select it through Pick a NetSuite list…. If it is missing, use Can't find it? Enter a custom list ID, enter the correct list ID, then select Load options. Find custom list IDs in NetSuite under Customization > Lists, Records, & Fields > Lists, in the ID column; this is the list ID, not an individual option’s internal ID. See Oracle’s custom list IDs. Use Refresh to request the options again. If options display as IDs, use the verified ID from NetSuite rather than guessing the label.
You can match values from custom dropdown and radio fields. Map values is not enabled for ordinary text fields, system dropdowns or multi-select fields. The dedicated NetSuite Contact ID and NetSuite Training Class ID source fields already contain IDs and do not need their values matched again.
Check fields with fixed choices
If a mapping row shows Preview List, select it. Picklist Values shows the choices NetSuite provided for that field. Use an accepted value in Cademy. This window only shows the choices; it does not match them to Cademy values. If it says No picklist values were provided for this field., have your NetSuite administrator confirm the allowed values.
Addresses and dates
A Cademy address field is split into selectable parts prefixed by the field name, such as “Office address: Region”. The parts include Address Line 1, Address Line 2, City, Region, Postcode and Country. Map individual parts to the matching supported NetSuite address fields. Contact address mappings build one address entry, not a separate entry for every address part.
Dates and date/time source fields are sent as calendar dates. Time-of-day information is not preserved. Some date/time values are converted using UTC, which may be a different calendar day from your local time. Check dates close to midnight in NetSuite before relying on the mapping.
Create a Cademy field while mapping
Use an existing field if it already holds the information you need. Choose a field that holds one value, such as text, a number, a date or a single-choice dropdown. Checkbox and multi-select answers are not sent to NetSuite. If you need a new field, this option is available for Contacts, Organisations, Courses and Occurrences:
In the mapping row, open Cademy Field and select Create new field….
Choose the field type. Enter its name in Label. Leave Internal Field Name blank to use the same name in the admin dashboard, or enter a separate name there.
For a dropdown or radio field, enter at least one choice in Items, one per line. Complete any other settings you need. Change Type returns to the type choices.
Select Create Field. The new field is selected in the mapping row.
Select its NetSuite field, match choices if needed, then select Save on the module page.
Create Field creates a real Cademy field immediately. Saving the mapping is a separate step. Existing records will not have values in the new field until you fill them in.
Check the first contact and course-date sync
After saving the mappings, use a record set aside for testing, or make a real update you already need to make. These actions send real records to every Ready connection with that module enabled. “Alex Example” below is a fictional name for your test contact.
As a System Admin, open Contacts > New Contact. In Contact Details, enter a test person's details, for example “Alex Example”, using an email address you control and do not already use for another contact. Complete any required fields, then select Create Contact. Wait for Contact created. See Manage Contacts for contact access and editing instructions.
Open Apps > NetSuite > your connection > Sync Activity and find the Contact. Reload the page if the result has not appeared. Check for Synced and note the number after NS:. This is the NetSuite internal ID; it is not a clickable link.
In NetSuite, open Lists > Relationships > Contacts. Find the contact and compare its internal ID and mapped values. To show IDs in lists, open Home > Set Preferences > General. Under Defaults, enable Show Internal IDs and save your preferences. Then return to Contacts. See Oracle’s Contacts guide and internal ID instructions.
To check Occurrences, use a course date you are authorised to edit. Open Courses and hover over the view icons to find Date List View, then select it. Find an individual course date, not a row marked Block, open its three-dot More actions menu and select Edit Date. This requires Course Owner access or a higher role. Update the intended field, then select Save. Use a date set aside for testing if this is only a check; saving an unchanged record is not a reliable test of an update.
Return to Apps > NetSuite > your connection > Sync Activity. Find the Occurrence, check Synced and its NS: ID, then open the NetSuite page agreed with your administrator. Find that ID and check the mapped values.
Correct any Failed result before moving on to certificates that depend on those records. Do not bulk-edit real records solely to force a historical import.
Prepare certificate links
If your NetSuite certificate record links to a contact or training class, configure those syncs on the same connection first.
Save the Contacts and, where needed, Occurrences mappings.
Confirm the relevant contact and course date have reached Synced in that connection's Sync Activity.
Open Mappings > Certificates, enable Certificates Sync, and select the destination certificate record type.
Map the certificate's Issued date, Expiry date and other required values. To link the person, select Contacts as the Cademy Module and NetSuite Contact ID as the Cademy Field. To link the course date, select Occurrences and NetSuite Training Class ID. Choose the matching reference fields in your own NetSuite certificate record.
Select Save before issuing the certificates you want to sync.
These IDs come from the contact and course-date syncs on this same connection. Keep the corresponding Contacts and Occurrences mappings enabled.
If the certificate is linked to a block’s parent record, it does not take a NetSuite Training Class ID from the block’s individual sessions. The parent record itself is not synced.
If the related Cademy record exists but its NetSuite ID is unavailable, the link is left out. A required NetSuite link can then cause a failure; an optional one can remain blank even when the row says Synced. Missing course-date, Registration or Order data can also leave out values.
A missing mapped Contact or Course is different. If the certificate mapping reads one of these records and it no longer exists in Cademy, the certificate sync fails. Check Last error for Contact no longer exists in Cademy. or Course no longer exists in Cademy. Check the saved NetSuite fields as well as the sync status.
For how to issue a certificate in Cademy, follow Certificates. Sending a certificate email is separate from syncing its information to NetSuite.
Check the result and retry failures
Open Apps > NetSuite and select the connection card.
Select Sync Activity.
Review Status, Object, Last attempted and Last error. The Object column includes the NetSuite ID as NS: when one is recorded. Hover over a shortened Last error message here to read it in full.
Use All Statuses, Synced, Failed or Needs reconnect to filter the visible records.
In NetSuite, use Lists > Relationships > Contacts for standard contacts, or the custom record page agreed with your administrator. Find the number shown after NS: and check the saved values.
Synced means NetSuite accepted the create or update. It does not mean every field was filled in. Check a contact, course date and certificate in NetSuite, including their links and dates.
Failed means an attempt failed. Read Last error, correct the data, mapping or NetSuite permission it identifies, then select Retry on that row. Retry uses the current Cademy record and saved mapping. Confirm the refreshed row says Synced; the message Sync record retried alone does not confirm success.
Needs reconnect means the connection’s login or access check failed. The connection also changes to Needs Reconnect, so new changes across its modules stop syncing until the connection is Ready again. Repair it as described below. This row does not offer Retry in the current interface.
Not attempted means there is no completed attempt recorded. No sync attempts yet means this connection has no activity rows. Check that the relevant module is saved and enabled, the destination is selected, and a contact or course date was created or changed, or a certificate was issued, after setup.
Each row shows the latest result for that record and destination. A later sync updates the same row; earlier errors are no longer shown after it succeeds.
The page shows up to 100 recently updated records for this connection. Filters and counts only cover those records, so older failures may not appear. There is no Load more or full attempt history here. Reload the page to check for later results.
Edit, pause or disconnect a connection
Replace credentials or reconnect
Open Apps > NetSuite.
Open the connection card's three-dot menu and select Edit Connection.
In Edit NetSuite connection, check the prefilled account details. Re-enter Consumer Key, Consumer Secret, Token ID and Token Secret; saved credentials are not filled back into these fields.
Select Test & continue, then Update connection, then Finish.
Confirm the card says Ready. Open the card and check Sync Activity for subsequent results.
Use Edit Connection when replacing keys or tokens for the same NetSuite account. To use a different NetSuite account, add a separate connection and configure its mappings, so Cademy does not try to update the wrong records.
Reconnecting does not send records missed while the connection was unavailable, or change old Needs reconnect rows to Failed. A new contact or course-date change can start another sync once the connection is Ready. There is no self-service Retry action for a Needs reconnect certificate row, or a button to send all missed certificates. Do not revoke and reissue a real certificate simply to test the integration.
Pause one module
Open Apps > NetSuite > your connection > Mappings, open the module, turn off its Sync switch and select Save. This stops that module on this connection. It does not delete records already sent to NetSuite. Turning it on and saving again allows new changes to sync. It does not send the records missed while it was off.
Disconnect the account
Open Apps > NetSuite, open the connection card's three-dot menu and select Disconnect. Read Disconnect NetSuite connector, then select Disconnect to confirm. The card changes to Disconnected and future syncs to it stop.
Disconnecting keeps the connection’s mappings and activity and does not delete NetSuite records or revoke the token in NetSuite. You can reconnect through Edit Connection with valid credentials.
Troubleshooting
The connection test fails
Check the Account ID and Realm against Setup > Company > Company Information. Check that both credential pairs belong to the same account, application, user and role, and that you copied each full value into the correct field. Keep Signature Method set to HMAC-SHA256 and leave the Advanced URL fields blank unless your administrator supplied them.
In NetSuite, verify the integration is Enabled, the user is active, the token is valid, and the role has the REST and token permissions described above, including access to Contacts. A sandbox refresh requires new tokens. Replace the credentials in Cademy and run Test & continue again. A missing record permission can cause an access error even when the keys are correct.
A destination, field or list will not load
Confirm the connection is Ready. Use Load All NetSuite Modules in the destination selector if you have only the initial suggestions. Ask your NetSuite administrator to check that the record type is available to integrations and that this connection’s role can access it. For a linked field, check the list ID and access to that list’s records. If a Cademy field is missing, check whether it is already used in another mapping row. Fields shown as unavailable cannot be enabled by retrying.
Save is unavailable
Save is disabled when nothing has changed or a mapping row is unfinished. Complete both the Cademy field and NetSuite field in every row, or remove the unfinished row with its bin icon. Value mappings need Save changes in their window and Save on the module page.
A record is missing or a field is blank
Check the correct connection and saved module first. Records created before setup are not automatically imported. Block parent course dates and revoked certificates are skipped. A certificate without a course date, Registration or Order cannot supply fields from that missing record.
Check whether the Cademy record has a value and whether the field type is supported. Missing or unsupported source values can be left out. For a linked NetSuite field, check every choice in Map values: an unmatched choice is sent unchanged as an ID and can cause a failure. Removing a mapping or a missing value does not reliably clear an old NetSuite value. Correct the destination separately when a value must be removed.
If a certificate's contact or training-class link is blank, check those records' NetSuite IDs on the same connection and confirm their mappings remain enabled. A previously Synced certificate does not get a Retry button simply because its mapping changes.
NetSuite reports an invalid value or required field
Read Last error to identify the field. Supply the required Cademy value, add its mapping, or have the NetSuite administrator set the correct destination default. For a reference, map a custom dropdown/radio value to the correct internal ID. For a field with fixed choices, use Preview List to see the values NetSuite provided, then use an accepted value. Save the mapping, then Retry a Failed row and inspect its new status.
NetSuite reports a request limit or temporary service error
NetSuite limits how many requests it can handle at once. If a temporary error leaves the row at Failed, wait, select Retry, then check the result. Do not assume a Failed row will retry itself later.
Frequently asked questions
Can I connect more than one NetSuite account?
Yes. Use + Add Connection and set up mappings separately for each account. New or changed contacts and course dates, and newly issued certificates, are sent to every Ready connection with that module enabled. A “default sync target” message on the first connection does not restrict syncing to that connection alone.
Does Cademy sync invoices, payments or all Orders to NetSuite?
No. The modules are Contacts, Occurrences and Certificates. Order information available within certificate mappings does not create a separate order, invoice or payment sync.
Will deleting a Cademy record remove it from NetSuite?
No. Deleting a record in Cademy does not delete it in NetSuite. Certificate revocation also does not automatically revoke or delete the record already created in NetSuite. Manage that destination record according to your NetSuite process.
Can I change the destination record type later?
Yes, but changing it clears that module's existing field mappings after confirmation. Rebuild the mappings and save. Existing NetSuite records remain, and future syncs can create records in the new destination. A Retry on an older Failed row still uses that row's original destination record type, so do not treat a destination change as a way to move or retry old records into a different type.
Why are the dropdown choices in Cademy different after mapping values?
Saving the Map values window updates the selected custom dropdown or radio field's options. Review additions and removals there before Save changes; these are shared field choices, not a private list used only by the integration.