# FR : Dynamic Link node enhancement request

**URL:** <https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179>\
**Category:** Feature Requests\
**Created:** [16 July 2022 07:48 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179 "2022-07-16T07:48:55Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![SandeepA](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sandeepa/32/63225_2.png) [@SandeepA](https://discourse.nodered.org/u/SandeepA)\
**Post date:** [16 July 2022 07:48 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/1 "2022-07-16T07:48:55Z")

</div>

Hi,

I would like to put a request for enhancement of Link Call Node (Dynamic call part).  
If the team can put it on their backlog list - that will be swell.  
(This is in line with my note on v3 Beta releases. )

1. Make the Dynamic Link Call more extensible - in terms of the param used for name of Link node.

Current Scenario :- With current mechanism of Dynamic Link call user needs a set node before every Dynamic Link Call - to set msg.target . If the flows have multiple dynamic different calls - then before each call msg.target needs to be set.

Proposal :- When user selects dynamic target ... he can type/select the called Link In node name from any options (string/ msg attribute/ flow variable/global variable / env variable / Jsonata expression ) - with default being msg.target if no such option is selected for dynamic target.

Since anyways this is a dynamic call - all of above options can qualify. Hope i could convey my thoughts. I dont know what is such a drop down called in NR language.

This will avoid the need to set msg.target before a Dynamic Link Call. Thereby reducing nodes in a flow.

1. Allow an option to have the Dynamic Link Call as a pass through.

We may have scenarios in a flow where based on condition - we may want to have the dynamic call will be just a pass through . The benefit here to avoid multiple - if and then conditions - before the call to dynamic link call.

This option will work in conjunction with Dynamic Link Call only.

So if user chooses dynamic Link Call + pass through option - in such scenario if the target Link In node doesn't exist - the Dynamic Link Call will not fail but move to the next node as per flow. It will act as a pass through node.

Once again Thank You for the amazing work which the NR development team is doing. Kudos to You guys.

Thank You so much.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [16 July 2022 09:14 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/2 "2022-07-16T09:14:43Z")

</div>

> [@SandeepA](#):
>
> Make the Dynamic Link Call more extensible - in terms of the param used for name of Link node.

What you are trying to describe is to use a `typedInput`  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/2/42a901fb36143e7712387a5f9bdf0c601226af03.png)

I think this is a reasonable request - lets see what others say.

  

> [@SandeepA](#):
>
> Allow an option to have the Dynamic Link Call as a pass through

How do you see this working? Currently, if the target does not exist we raise an error. This was a deliberate design decision so that users can `catch` errors and not permit a `msg` to pass through without being "processed".

  

My addition...

Somewhere on the forum or github as user has requested the "link out" node have similar capability. I am pretty sure I will NOT be adding this feature BUT if we permitted the `link call`s timeout to be disabled, the same result could be achieved. e.g. `inject -> link call -> link in -> flow to execute`

---

<div class="post-metadata">

**Author:** ![SandeepA](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sandeepa/32/63225_2.png) [@SandeepA](https://discourse.nodered.org/u/SandeepA)\
**Post date:** [16 July 2022 12:11 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/3 "2022-07-16T12:11:46Z")

</div>

> [@Steve-Mcl](#):
>
> What you are trying to describe is to use a `typedInput`

Yes. This is exactly what i meant. I wasnt 100% sure of the term "typedInput". so did not mention it Thank You.

> [@Steve-Mcl](#):
>
> How do you see this working? Currently, if the target does not exist we raise an error. This was a deliberate design decision so that users can `catch` errors and not permit a `msg` to pass through without being "processed".

Technically (I have not gone through the code ), i would assume if passthrough is selected & dynamically called link in node not found - then instead of "throw" it would be node.send(msg) sending the msg ahead. If not selected - it continues to throw error.

If the user selects pass through - he knows he will no longer get error . If passthrough is not selected the current behavior continues. By having pass through toggle (tickbox) - you give the decision to the user.

Default behavior remains like today - error gets thrown if link in doesn't exist.

Maybe prioritize the typedInput - if bandwidth is available - and pass through can be in next iteration.

---

<div class="post-metadata">

**Author:** ![SandeepA](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sandeepa/32/63225_2.png) [@SandeepA](https://discourse.nodered.org/u/SandeepA)\
**Post date:** [23 July 2022 19:09 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/4 "2022-07-23T19:09:17Z")

</div>

Hi @Steve-Mcl - Would you know if this will make it to the backlog list ? At least part #1.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 July 2022 19:50 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/5 "2022-07-23T19:50:05Z")

</div>

I'm not 100% certain. However, if you were to raise a PR it would certainly stand a chance of making v3.1. otherwise, just remember to nudge me on a weekly basis 😉

---

<div class="post-metadata">

**Author:** ![SandeepA](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sandeepa/32/63225_2.png) [@SandeepA](https://discourse.nodered.org/u/SandeepA)\
**Post date:** [23 July 2022 19:58 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/6 "2022-07-23T19:58:18Z")

</div>

How can i raise a PR - can you share with me the process - and i will give it a shot. Thanks.

---

<div class="post-metadata">

**Author:** ![SandeepA](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sandeepa/32/63225_2.png) [@SandeepA](https://discourse.nodered.org/u/SandeepA)\
**Post date:** [7 August 2022 21:44 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/7 "2022-08-07T21:44:17Z")

</div>

Hi Steve,

I checked the process to raise a PR and as i can make out - it needs to do a design into the internals of the code. If so - i am a bit out of depth here.

Irrespective - gentle nudge on this change.

Tx.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [6 October 2022 21:44 UTC](https://discourse.nodered.org/t/fr-dynamic-link-node-enhancement-request/65179/8 "2022-10-06T21:44:57Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.