Questions on Custom Attribute Mapper Column Limit and Multiple CAMs in NSAW

Question

Hi Team,

We are working on Custom Attribute Mapper (CAM) configuration in NetSuite Analytics Warehouse (NSAW) and have a few questions.

* While creating a Custom Attribute Mapper, we receive an error when selecting more than 100 columns. Could you please confirm whether this is a product limitation?
* Is there any way to increase this column limit through an environment setting or with administrator assistance?
* Can multiple Custom Attribute Mappers be created for the same source object (for example, Customer Invoice Transactions), where one CAM contains the first set of columns and another CAM contains additional columns?
* In our environment, we do not see an option to provide a custom name for the mapper. Does NSAW support only one CAM per source object?
* If only one CAM is allowed per source object, what is the recommended approach for handling more than 100 custom fields? Should we use Data Augmentation for the remaining attributes?
* This configuration appeared to work in our previous sandbox. Could there be any version or environment differences that explain this behavior?

We would appreciate any documentation or best-practice recommendations for handling a large number of custom fields in NSAW.

Thanks,

Chandra

Aljan Patrick Mendoza-Oracle · Accepted Answer

Hi Chandra,

I reviewed Oracle’s official documentation and current product behavior. Below are detailed answers to each of your questions, along with supporting documentation and recommended best practices.

* Is the 100-column selection limit in Custom Attribute Mapper a product limitation?

Yes. Based on current product behavior, the inability to select more than 100 attributes in a single Custom Attribute Mapper is a product limitation.

Although Oracle’s official documentation for Custom Attribute Mapper does not explicitly state a “100-column” maximum, multiple customer environments consistently enforce this limit in the UI. Once approximately 100 attributes are selected, the Save operation fails with an error.

Oracle documentation confirms that CAM is designed to “select the attributes you want to associate with the source transaction type,” but it does not mention any configurable setting to raise the maximum number of selected fields.

Document: https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawa/map-custom-attributes1.html

2. Can this limit be increased through an environment setting or administrator action?

No known configuration setting exists to increase the 100-column limit.

Unlike the documented 4,000-character attribute size limit which Oracle explicitly notes can sometimes be addressed by modifying the source field size or working with administrators the column-count limit is not documented as configurable.

As of current releases, this appears to be a hard-coded application constraint rather than an environment parameter that can be adjusted by:

If your business requirement exceeds this limit, we advised to reach out to your AMO and ask to create a oracle/netsuite case.

3. Can multiple CAMs be created for the same source object?

In standard NSAW functionality, only one Custom Attribute Mapper is supported for each source object and level.

For example:

* Customer Invoice Transactions (Header)
* Customer Invoice Transaction Lines
* Customer Entity

When creating a CAM, the system generates a single mapping definition for the selected source object. The UI does not provide a field to assign a custom name, which strongly indicates that the source object itself uniquely identifies the mapper.

This behavior aligns with Oracle’s documentation, where the process is described as selecting a source transaction or entity and associating attributes with it, rather than creating multiple independently named mappings.

4. Why is there no option to provide a custom name for the mapper?

CAM definitions are system-managed and keyed by the selected source object rather than by a user-defined name. Because of this design:

* No custom naming field is displayed.
* Only one CAM exists per source object.
* Reopening the source object allows you to edit the existing mapper rather than create a second one.

5. What is the recommended approach when more than 100 custom fields are required?

If you need to expose more than 100 custom fields for the same source object, Oracle’s recommended approach is to supplement CAM with Data Augmentation.

Recommended Strategy

Use CAM for:

* Most frequently used reporting attributes
* Fields required in subject areas and semantic model extensions
* Common business dimensions

Use Data Augmentation for:

* Additional custom fields beyond the CAM limit
* Complex joins
* Fields referencing other transaction internal IDs
* Specialized reporting requirements

Oracle documentation explicitly states that some unsupported attribute types (such as fields referencing other transaction internal IDs) should be brought into NSAW using Data Augmentation.

Best Practice

A practical design is:

* Select the top 100 highest-value custom fields in CAM.
* Publish the mapper.
* Use Data Augmentation to load the remaining fields.
* Extend the semantic model if needed to expose those fields to use

6. Could sandbox and production environments behave differently?

Yes, several factors can explain why this appeared to work in another sandbox:

Possible Reasons

1. Different NSAW release versions

Oracle updates NSAW quarterly, and behavior can change between versions.

2. Different source object selections

A prior environment may have had fewer valid or visible fields.

3. Previously created mappings

Existing mappings might have already included a subset of fields.

4.UI validation changes

Oracle may have introduced stricter enforcement in recent releases.

5.Permission differences

Roles and metadata visibility can affect available attributes.

To confirm, compare the release levels shown in the What's New for Oracle NetSuite Analytics Warehouse documentation and verify that both environments are on the same NSAW version.

Document: https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawn/whats-new-oracle-netsuite-analytics-warehouse.pdf

References:

https://community.oracle.com/netsuite/english/discussion/4491439/how-to-use-the-custom-attribute-mapper-cam

https://community.oracle.com/netsuite/english/discussion/4491432/when-to-use-the-custom-attribute-mapper-cam

https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawn/whats-new-oracle-netsuite-analytics-warehouse.pdf

https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawa/administering-oracle-netsuite-analytics-warehouse.pdf

https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawa/extend-data-custom-data-configurations.html

https://docs.oracle.com/en/cloud/saas/netsuite-analytics-warehouse/nsawa/map-custom-attributes1.html

Best Regards,

AljanPatrick Mendoza

ORACLE NETSUITE| NSAW -Netsuite Support