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

Comments

3 comments

  • Tyler Lamparter Principal Product Manager
    Awesome Follow-up
    Engaged
    Top Contributor
    Answer Pro
    Celigo University Level 4: Legendary

    Geoff Tipley 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. 

    0
  • Geoff Tipley NetSuite Integration Whiz
    Celigo University Level 4: Legendary

    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.

    0
  • Tyler Lamparter Principal Product Manager
    Awesome Follow-up
    Engaged
    Top Contributor
    Answer Pro
    Celigo University Level 4: Legendary

    Geoff Tipley 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.

    0

Please sign in to leave a comment.