Why is usage of integration-level `settings` object so restricted?

Integrator.io
, , , ,
1

The integration-level `settings` object is strangely unusable and unavailable for something that is a sort of "global" settings for the integration. Why is it like this?

For integrations with NetSuite, I like to use this as Configuration for the environment, so that I can clone a flow from Sandbox to Production, and it can just reference the integration's settings for Account numbers, location numbers, class numbers, and sometimes static data in JSON format without me having to make any changes to the flow after it switches environment. Ideally, I'd even be able to select Saved Searches for various Lookups there so that I don't have to select them in each lookup of the flow every time I deploy a new version of it to Production.

But to actually use any of that Settings data, I have to write a Script to attach settings.integration to each record, and reference it there, and I suspect Integrator's inability to use this data in Mock Outputs is the cause of missing and broken preview data an old, non-branching flow of mine.

Where is settings.integration data meant to be used? I think I recall that one can make reference to it in the Source export but is that all?

2

@geofftipley the end goal would be to have the ability to use handlebar expressions for almost every field so that the settings could be used anywhere. I recognize some of the NetSuite fields like saved search id and record type don't allow handlebars, but outside of those fields, where else would you like to use settings? Knowing where you're trying to use it would be helpful for us to prioritize migrating fields over to accept handlebar input.

Outside of the additional fields you need, you don't have to use a script to access the settings. The settings are available wherever a field accepts handlebar expressions and when using AFE 2.0.

5301043caa20740200000001-a3ed5fa2b4b64c9fb008b8712cf13b8c.png
5301043caa20740200000001-a3ed5fa2b4b64c9fb008b8712cf13b8c.png2537×1253 193 KB

5301043caa20740200000001-27fe1c6a7ba9494a8857f5e546879f2e.png
5301043caa20740200000001-27fe1c6a7ba9494a8857f5e546879f2e.png2514×1104 116 KB

3

In addition to Saved Search settings, I've wanted to use settings in Mappings, for instance to set the Revenue Recognition account on a NetSuite Invoice's item lines.

4

@geofftipley thanks for the feedback. Because NetSuite is still using Mapper 1.0, the settings are unavailable. Once it's migrated to Mapper 2.0, the settings will be available there just as they are for anything else using mapper 2.0. I don't have an ETA on enabling Mapper 2.0 for NetSuite, but it's on the roadmap.