Skip to main content

Create HTTP import mapping with static or dynamic lookup

Comments

8 comments

  • Tom Santiago Principal Technical Writer Community moderator
    Engaged
    Top Contributor
    Celigo University Level 4: Legendary

    For more information on how you can use advanced lookups in tandem with response mappings, take a look at this article: Response mapping and advanced lookups.

    0
  • Ricko Borja Technical Support Representative
    Great Answer
    Celigo University Level 4: Legendary

    Confirmed that the Create HTTP import mapping with static or dynamic lookup doesn't include the actual valid handlebar expression by adding single quotes on the "lookup name". The following should have the actual Lookup handlebar syntax:

    • Dynamic lookup: {{lookup '<lookup name>' this}}
    • Static lookup: {{lookup '<lookup name>' this.<Export Field Name>}}

    Just provide the <lookup name> and <Export Field Name> and that should work. The HTTP Lookup Preview might not show the correct details (i.e., "{ASYNCID$0$8$}") though this is just a Preview interpretation. Running the flow would confirm the actual results of the lookup.

    0
  • Tom Santiago Principal Technical Writer Community moderator
    Engaged
    Top Contributor
    Celigo University Level 4: Legendary

    Thanks Ricko Borja, I revised the article per your correction.

    Tom

    0
  • Steve Klett Strategic Partner
    Celigo University Level 4: Legendary
    Answer Pro
    Great Answer
    Top Contributor
    Awesome Follow-up
    Engaged

    When I click on an HTTPS Import I don't have an import mapping icon. I've ready the beginning of this page a couple times to make sure I'm not missing something? When I click on the "+" icon on the HTTPS Import my only options are: Transformation, Output Filter and Hook.

    0
  • Stephen Brandt Documentation Manager Community moderator
    Engaged
    Great Answer
    Top Contributor
    Celigo University Level 3: Master

    Hi, Steve Klett. Is the import a file transfer (upload)? That would be the expected behavior, if so; the "mapping" is done in the request body. Otherwise, we need to have someone look at your flow and delve a little deeper.  

    0
  • Steve Klett Strategic Partner
    Celigo University Level 4: Legendary
    Answer Pro
    Great Answer
    Top Contributor
    Awesome Follow-up
    Engaged

    Stephen Brandt, your question made me look into this and I see what's happening. The API I'm calling is terrible and uses GET requests with URL params to do everything. So although I'm creating orders in their system I need to use HTTP GET to accomplish it. This forces me to create a lookup type HTTP import which is why there isn't any mapping. If I choose an Import type HTTP node the GET method isn't available.

    For what it's worth, here's a real world example with a pretty large 3PL where the IIO (integrator.io) tools don't 100% fit the requirements (i.e., import using a GET).

    Thanks for the reply!

    0
  • Stephen Brandt Documentation Manager Community moderator
    Engaged
    Great Answer
    Top Contributor
    Celigo University Level 3: Master

    Thanks, Steve Klett, for pointing me in the right direction. I'll share your feedback and use case with mapping product management. Sorry about the extra work you're having to do. 

    0
  • Steve Klett Strategic Partner
    Celigo University Level 4: Legendary
    Answer Pro
    Great Answer
    Top Contributor
    Awesome Follow-up
    Engaged

    I appreciate you taking the feedback to the crew - no need to apologize, the tool will get better and better!

    0

Please sign in to leave a comment.