nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

RE NXT Full Page Add-in

Alex Wong

Hi,

I was able to follow the instruction on this page to create a full page add-in to RE NXT:

So the full-page to be displayed is actually sourced from a PowerAutomate HTTP request received trigger flow. The method is GET.

When setting up the full page add-in:

e12164f9d7fa3dd5694d5bcc35f9a5d9-huge-im

I placed the URL of the HTTP request received trigger flow in the Add-in URL box.

I then added another add-in that is a home page action to this page add-in.

All is working well, the action show up under task, clicking on it opens up the full page served by the flow.

Now I want to add validation and is stuck. With a Tile, the request to the “back-end” flow is done through POST and with it is the uit parameter. However, when I change to method of POST on my flow and add the json schema, I get error in my console that the page was trying to do GET and failed.

Maybe I'm going about it totally wrong here, please let me know how I can get uit for a page add-in

Thank you,

Alex

Find more posts tagged with

Comments

Alex Wong

@Glen Hutson

after looking more into this, and then studying your AIO more, I have a feeling this is a limitation currently with SKY Add-in. which is the reason why you went with the “AIO” route where multiple “calls” was done within the original GET requested page b/c the original GET requested page can obtain the UIT from the JS client object, then pass it as query parameter to subsequent call.

Let me know if my understanding is correct here and there isn't an easier way to do this.

Glen Hutson

@Alex Wong:
@Glen Hutson
after looking more into this, and then studying your AIO more, I have a feeling this is a limitation currently with SKY Add-in. which is the reason why you went with the “AIO” route where multiple “calls” was done within the original GET requested page b/c the original GET requested page can obtain the UIT from the JS client object, then pass it as query parameter to subsequent call.
Let me know if my understanding is correct here and there isn't an easier way to do this.

You're correct. When calling most, if not all, add-ins directly without going through a pre-made Host SPA, it's GETs all the way and the UIT is typically available via a POST.