Global and extra constants name error
Comments
-
Hi Support,
I have a series of global constants that I have setup on my primary instance, and are also used on my tennants on that instance. However i seem to be getting the following warning in my logging directory, is there a reason for this / something that im doing wrong here?
[b]Category : [/b]FlowConstant
[b]Level : [/b]Warn
[b]Exception: [/b][Message]:Global and extra constants have a constant with the same nameThanks in advance!
[i]edited by KempthamL on 7/22/2020[/i] -
Hi Lee,
In relation to Global Constants with the same name, the key here is whether or not that value exists on the Primary. You can create a variable with the same name across multiple tenants, and it will work as you would like it to as long as that same name does NOT exist on the Primary. If it exists on the primary, then the value given for the Primary will be the one that is used. Naming global constants the same across all tenants is our best practise recommendation, we would advise this over storing them on the Primary instance itself.
Howdy, Stranger!
Categories
- 4.2K All Categories
- 68 General
- 11 Training
- 203 Installation / Setup
- 1.1K Flows
- 108 Rules
- 262 Administration
- 212 Portal
- 494 General Q & A
- 699 Forms
- 334 Reports
- 3 Designer Extensions
- 47 Example Flows
- 53 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 180 Pages
- 5 Process Mining
- New Features
- 180 Datastructures
- 69 Repository
- 221 Integrations
- 28 Multi-Tenant
- 27 SDK
- 80 Modules
- 56 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 92 Lunch And Learn Questions