Getting weired error in flow designer

Vinay2509
Tera Contributor

Hi Team,

 

We are facing below error pop up , when we test the flow, we have verified its working for some not for some with though having same role

 

please advise to resolve

 

 

 

Vinay2509_0-1710245963998.png

 

Vinay2509_1-1710246092776.png

.

 

1 ACCEPTED SOLUTION

Ahmed Drar
Tera Guru
Tera Guru

Hi @Vinay2509 ,

 

I experience the same issue and apply a workaround.

 

the workaround is to call  TNIConstants that is in sn_ni_core rather than the one in sn_ni_adv which is not a great workaround but it works.
 
Here is example of one line code to make sure TNIConstants is being called from sn_ni_core scope rather than the one in sn_ni_adv scope : -
TNIConstants = sn_ni_core.TNIConstants
 
 

I hope this helps.

Ahmed

Please mark my answer as Correct / Helpful based on the Impact

 

View solution in original post

4 REPLIES 4

Sandeep Rajput
Tera Patron
Tera Patron

@Vinay2509 This error is regarding a Script Include TNIConstants not defined. Please see if any script include with name TNIConstants defined on your instance and it is being called within your flow.

@Sandeep Rajput I have not used any names used in TNIconstant (OOB).. 

 

I have created flow when aim is to create instance of ABC device and create Physical connection

 

This occurs some time and sometimes not

Aneesh-D
Tera Guru
Tera Guru

@Vinay2509  -

 
TNIConstants is a OOB server side script in TNI Network Inventory Core and Network Inventory Advanced.
you can verify this in system definition>script includes
 
AneeshD_0-1710718504737.png

Can you check if this is available in your script include?

 

The issue seems to be on "Operation OMT-TNI Flow To Get Connection By Serial Number" . Can you verify if there is any issue with this flow?

 

Ahmed Drar
Tera Guru
Tera Guru

Hi @Vinay2509 ,

 

I experience the same issue and apply a workaround.

 

the workaround is to call  TNIConstants that is in sn_ni_core rather than the one in sn_ni_adv which is not a great workaround but it works.
 
Here is example of one line code to make sure TNIConstants is being called from sn_ni_core scope rather than the one in sn_ni_adv scope : -
TNIConstants = sn_ni_core.TNIConstants
 
 

I hope this helps.

Ahmed

Please mark my answer as Correct / Helpful based on the Impact