Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Duplicated id for trigger ourput

D

HI community,

In my system users can create their own fields and call it as they wish. The only restriction is using _ at the beginning because that’s how we represent the id of the data. Since every output trigger needs an id, I was just converting the _id to the id field, but this creates a conflict when a user has an id in their data. Like this:

{
 _id: '123123',
 id: '2'
}

My questions is if there is a good solution for solving this problem.

I was thinking about not using the _id for the output id but I wouldn’t use what to use instead.

Thank you! 

 

Best answer by Diego Orca

I fixed the issue encapsulating the data into an object like this:

{
 id: '1',
 data:{
   id: 'example1',
   name: 'example'
  }
}

 

View original
    Did this topic help you find an answer to your question?
    This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

    2 replies

    GetUWired
    Forum|alt.badge.img+12
    • GetUWiredZapier Expert
    • Zapier Expert
    • 1030 replies
    • August 4, 2022

    @Diego Orca 

    Might not be the best solution but the simplest might be just to preserve the ‘id’ field to a new key prior to overwriting it with the ‘_id’ field?

    D
    1 person likes this
    • D
      Diego Orca
    D
    • Diego OrcaBeginner
    • Author
    • Beginner
    • 1 reply
    • Answer
    • August 9, 2022

    I fixed the issue encapsulating the data into an object like this:

    {
 id: '1',
 data:{
   id: 'example1',
   name: 'example'
  }
}

     

    Terms & Conditions