#Prompt Field(%GlobalData) not showing %GlobalData fields but From(%GlobalData) does - Bug?

questions
,
1 
#Prompt('Global Process ID Field (Required) : ',From(%GlobalData)),%ISADGlobalProcessID,Req - works
    #Prompt('Global Process ID Field (Required) : ',Field),%ISADGlobalProcessID1,Req - ellipse button disabled
    #!Prompt('Global Process ID Field (Required) : ',Field()),%ISADGlobalProcessID2,Req - Expected a statement, ',' expected, Expected a variable name 
    #Prompt('Global Process ID Field (Required) : ',Field(%GlobalData)),%ISADGlobalProcessID3,Req - ellipse button enabled - Need to specify a parent for this item first
    #Prompt('Global Process ID Field (Required) : ',Field(%GlobalDataID)),%ISADGlobalProcessID4,Req - ellipse button enabled - Need to specify a parent for this item first
    #Prompt('Global Process ID Field (Required) : ',From(%GlobalDataID)),%ISADGlobalProcessID5,Req - Drop down not showing anything

Should Field, Field(%GlobalData), Field(%GlobalDataID) and From(%GlobalDataID) work in a global extension template?

TIA

2

The templates have always been quirky, and I find that FIELD is one of the stranger features. Therefore, I’ll often use a #PREPARE section to load the options I want to see into a multi-valued symbol, then go FROM(%MySymbol). That gives me more control, and seems to work more predictably.

3

I feel like you can’t use FROM on a template-declared-variable. Only on a built-in variable.
But that may be an over-simplification, and I can’t recall exactly where I’ve used that.

I feel like though when I’ve got a template-declared variable I’ve used DROP not FROM.

4

No

#Prompt Entry Types are well documented in the Help.
FIELD [(scope)] is for FILE’s.
FROM(symbol) is for a Multi-Valued.

I often review the Help on #PROMPT as one of the most detailed

The best examples for template commands are found searching the shipping templates.

5

You can definitely #DECLARE(%SomeMultiVar),UNIQUE in a #PREPARE section, the use that via FROM(%SomeMultiVar) below that point in the prompts.

I’ve also filed that same list using WHENACCEPTED, if it will change the contents of the list. The two work in concert quite well.

Alternatively, you can define a hidden multi-valued prompt to use instead, but that shouldn’t be necessary here.

6

I havent tested, but I seemed to think that Globals could be accessed this way in C6 which is why I was asking.

Plumped for the Dropdown for now, its sufficient.

7

Yeah, there are definitely template features that worked differently in C6 than the later versions, but C6 is basically irrelevant now. :man_shrugging:

8

Not being able to populate a #Prompt(‘Proc name:’,Procedure) seems to be another one.