MULTIPLE CHOICE OPTION FIELD

sre

kash387 wrote:

So,
what's your problem now???

I just thought the same as there was no question included in the last post :-)

kash387

But Shona has already link the field with the custom table...!!!

Shonatina

kash387 wrote:

But Shona has already link the field with the custom table...!!!

i would seem real silly..the problem is the lookup isnt working! nor the drill down!..

sre

Shonatina wrote:

i would seem real silly..the problem is the lookup isnt working! nor the drill down!..

Did you define the LookupFormID in your lookup table?

Shonatina

realmen885 wrote:

We're making several improvements to the WOW user interface for tracking quest objectives in our 3.3 content update.

We're making several improvements to the WOW user interface for tracking quest objectives in our 3.3 content update. These new features will serve to improve the questing experience for players through a multitude of new tracking options. In the quest log, we've added up a new "Show Map" button on the WOW quest log. The "Show Map" feature highlights any quest in the log and will pull up the map for the zone in which the corresponding quest objectives are located Final Fantasy Gil.

When viewing the large zone WOW map, players will notice that all quests they have for that zone will be automatically tracked. In addition, now this large map is separated into four separate interface panes. To the right of the WOW map, all active quests for WOW Gold that zone will be listed by name and be represented with a number. These numbers will be placed on the map highlighting areas of interest for each quest.

A third pane below the zone map will give players the full quest text for any highlighted quest, while the fourth pane will display the questBuy WOW Gold reward. The quest map tracking feature is enabled by default. Players can disable this feature and restore the WOW map to its original state by un-checking the "Show Quest Objectives" box in the lower right corner. All areas of interest in a zone will be represented with a number corresponding to the number assigned to each active quest in that particular zone. When highlighting a specific quest, the corresponding number on the zone map will be highlighted as well Aion Gold.

If the area of interest is large, a player needs to kill a number of quest creatures or collect quest WOW items to find within a large area on the map, the entire questing area of interest around the number on the map will be shaded blue. If quest objectives can be accomplished in multiple areas of the zone, the certain creatures need to be killed for a quest and have several different locations; the WOW map will automatically display the nearest area of interest in proximity to the player Metin2 Gold.

is this a spam?

Shonatina

sre wrote:

Shonatina wrote:

i would seem real silly..the problem is the lookup isnt working! nor the drill down!..

Did you define the LookupFormID in your lookup table?

yes i did.....'m trying differnt ways here...will let you know how it turns out!

Shonatina

hi there,
i coded it like this with the same option field....

IF (gDropDownPrac IN [ gDropDownPrac :: NAV]) THEN BEGIN
IF (gdropdown IN [ gdropdown :: "Short Term"]) THEN BEGIN
gIntest.RESET;
gIntest.SETFILTER("Phase Type",'%1|%2',1,5);
IF gIntest.FINDSET THEN BEGIN
gEntryFilter.SETTABLEVIEW(gIntest);
IF (NOT gPm AND gSe AND NOT gPl AND NOT gTechnical AND NOT gTeamLeader AND NOT gFunctional AND NOT gExternal AND NOT gDev
)=TRUE THEN BEGIN
gEntryFilter.ApplyMyFilter(gPm,gPl,gSe,gTeamLeader,gDev,gFunctional,gTechnical,gExternal);
gEntryFilter.RUN;
END;
END;
END;
END;

kash387

So is it working????

Belias

Belias wrote:

](*,) sorry, but this is basic database design...the simplest way is to ask a more experienced developer, if there's one with you.
I've no time to guide you step by step, but probably someone else have it (note that having someone guide you step by step is a good way to learn NAV).

there's an errata in my previous post (the quoted one):
...step by step, but probably someone else have it (note that having someone guide you step by step is ***NOT!!!*** a good way to learn NAV).

Shonatina

kash387 wrote:

So is it working????

yup it is!...otherwise i wont post it here!.......i knew there was a way to use option field! thank you all................

Shonatina

Belias wrote:

Belias wrote:

](*,) sorry, but this is basic database design...the simplest way is to ask a more experienced developer, if there's one with you.
I've no time to guide you step by step, but probably someone else have it (note that having someone guide you step by step is a good way to learn NAV).

there's an errata in my previous post (the quoted one):
...step by step, but probably someone else have it (note that having someone guide you step by step is ***NOT!!!*** a good way to learn NAV).

Since i coded "THE SOLUTION" I needed for my problem...
Anyways thank you all...especially Kashyap & sascha

Belias

i found some time (stolen to my coffe break) to write how would i've solved your problem (it's a really stupid sample). hope this helps, and i hope i understood your request.
save the "code" part of this message and import as text. (table 60000 and 60001; form 60000 - be sure that this won't overwrite your own objects)
before having the whole thing working, you must open the form and populate all the wanted combinations, for example:
method1 -> development
method1 -> analysis
method2 -> analysis

this setup means that methodology1 allows both development phase and analysis phase, while method2 allows only analysis phase

then open "base table" (60000) -> this would be your screenshotted table and try to use the various methods to see what combinations are you allowed to use.

Note that i've not written a single line of code

OBJECT Table 60000 base table
{
  OBJECT-PROPERTIES
  {
    Date=13/07/10;
    Time=11.34.31;
    Modified=Yes;
    Version List=;
  }
  PROPERTIES
  {
  }
  FIELDS
  {
    { 1   ;   ;methodology         ;Option        ;OptionString=method1,method2,method3,method4 }
    { 2   ;   ;phase               ;Code10        ;TableRelation="phase/method relation".phase WHERE (appliable method=FIELD(methodology)) }
  }
  KEYS
  {
    {    ;methodology                             ;Clustered=Yes }
  }
  FIELDGROUPS
  {
  }
  CODE
  {

    BEGIN
    END.
  }
}

OBJECT Table 60001 phase/method relation
{
  OBJECT-PROPERTIES
  {
    Date=13/07/10;
    Time=11.36.13;
    Modified=Yes;
    Version List=;
  }
  PROPERTIES
  {
    LookupFormID=Form60000;
    DrillDownFormID=Form60000;
  }
  FIELDS
  {
    { 1   ;   ;phase               ;Code10         }
    { 2   ;   ;appliable method    ;Option        ;OptionString=method1,method2,method3,method4 }
  }
  KEYS
  {
    {    ;phase,appliable method                  ;Clustered=Yes }
  }
  FIELDGROUPS
  {
  }
  CODE
  {

    BEGIN
    END.
  }
}

OBJECT Form 60000 phase/method relation
{
  OBJECT-PROPERTIES
  {
    Date=13/07/10;
    Time=11.35.50;
    Modified=Yes;
    Version List=;
  }
  PROPERTIES
  {
    Width=9790;
    Height=6710;
    TableBoxID=1101366000;
    SourceTable=Table60001;
  }
  CONTROLS
  {
    { 1101366000;TableBox;220 ;220  ;9350 ;5500 ;HorzGlue=Both;
                                                 VertGlue=Both }
    { 1101366001;TextBox;0    ;0    ;1700 ;0    ;ParentControl=1101366000;
                                                 InColumn=Yes;
                                                 SourceExpr=phase }
    { 1101366002;Label  ;0    ;0    ;0    ;0    ;ParentControl=1101366001;
                                                 InColumnHeading=Yes }
    { 1101366003;TextBox;0    ;0    ;550  ;0    ;ParentControl=1101366000;
                                                 InColumn=Yes;
                                                 SourceExpr="appliable method" }
    { 1101366004;Label  ;0    ;0    ;0    ;0    ;ParentControl=1101366003;
                                                 InColumnHeading=Yes }
    { 1101366005;CommandButton;2530;5940;2200;550;
                                                 HorzGlue=Right;
                                                 VertGlue=Bottom;
                                                 Default=Yes;
                                                 PushAction=LookupOK;
                                                 InvalidActionAppearance=Hide }
    { 1101366006;CommandButton;4950;5940;2200;550;
                                                 HorzGlue=Right;
                                                 VertGlue=Bottom;
                                                 Cancel=Yes;
                                                 PushAction=LookupCancel;
                                                 InvalidActionAppearance=Hide }
    { 1101366007;CommandButton;7370;5940;2200;550;
                                                 HorzGlue=Right;
                                                 VertGlue=Bottom;
                                                 PushAction=FormHelp }
  }
  CODE
  {

    BEGIN
    END.
  }
}

Shonatina

Belias wrote:

i found some time (stolen to my coffe break)....

Thanks a Lot BELIAS
i will have a copy and make use when need comes!

Belias

I hope you'll use this sample to solve the issue you posted here, because your solution is hard to maintain, and hard to understand for other developers (you have to modify and retest your code every time a phase or method is added)
I also hope you've undertood how my sample works, in order for you to apply that "pattern" to similar cases.

Last note:
why you wrote

IF (gDropDownPrac IN [ gDropDownPrac :: NAV]) THEN BEGIN

instead of

IF gDropDownPrac = gDropDownPrac :: NAV THEN BEGIN

?

Shonatina

Belias wrote:

I hope you'll use this sample to solve the issue you posted here, because your solution is hard to maintain, and hard to understand for other developers (you have to modify and retest your code every time a phase or method is added)
I also hope you've undertood how my sample works, in order for you to apply that "pattern" to similar cases.

Last note:
why you wrote

IF (gDropDownPrac IN [ gDropDownPrac :: NAV]) THEN BEGIN

instead of

IF gDropDownPrac = gDropDownPrac :: NAV THEN BEGIN

?

i will let you in on a secret(which wont be 1 after this...lol) i wrote it like that because while i was coding my hand kinda started typing the codes...and these codes where the result! funny huh!...but Thanks again...i will use this method also!

And i cant use this solution now because i cant change my base requirement!....But thanks

Ryden

I know I'm eight years late, but there IS a way to have different optionstrings according to some criteria in a page.

You need to define your different sets of valid options
Then you need to design the same number of copies of your option field in your page
For each of these, you change the OptionCaption property eg.

(Example from a customization of Page 7004, three copies of "Sales Type" )

Copy 1: <Customer,Customer Disc. Group,All Customers,Campaign> (This is the original field with default optionstring)
Copy 2: Customer
Copy 3: ,Customer Disc. Group

Then you need to set a condition on Visible so that only one of these fields is visible, I've used the standard variable SalesTypeFilter

Copy 1: SalesTypeFilter > 1
Copy 2: SalesTypeFilter = 0
Copy 3: SalesTypeFilter = 1

Now if you open this from a Customer page, you can only insert customer discounts.
If you come from a Customer Disc. Group, that's the only type you can choose and if you open it from any other place you can insert any type of discount

Ryden

I tried to attach a textfile but only pictures seems allowed
Here's some 2017 snippets instead

    LOCAL PROCEDURE GetRecFilters@2();
    BEGIN
      IF GETFILTERS <> '' THEN
        // Customized
        //UpdateBasicRecFilters;
        UpdateBasicRecFilters
      ELSE
        SalesTypeFilter := SalesTypeFilter::None;
        // End
    END;



 { 32  ;2   ;Field     ;
                ToolTipML=[ENU=Specifies the sales type of the sales line discount. The sales type defines whether the sales price is for an individual customer, customer discount group, all customers, or for a campaign.;
                           SVE=Anger f”rs„ljningstypen f”r f”rs„ljningsradrabatten. F”rs„ljningstypen avg”r om f”rs„ljningspriset avser en enskild kund, en kundrabattgrupp, alla kunder eller en kampanj.];
                ApplicationArea=#Basic,#Suite;
                Description=Customized;
                SourceExpr="Sales Type";
                Visible=SalesTypeFilter > 1 }

    { 1100570002;2;Field  ;
                Name=SalesTypeCust;
                ToolTipML=[ENU=Specifies the sales type of the sales line discount. The sales type defines whether the sales price is for an individual customer, customer discount group, all customers, or for a campaign.;
                           SVE=Anger f”rs„ljningstypen f”r f”rs„ljningsradrabatten. F”rs„ljningstypen avg”r om f”rs„ljningspriset avser en enskild kund, en kundrabattgrupp, alla kunder eller en kampanj.];
                OptionCaptionML=[ENU=Customer;
                                 SVE=Kund];
                ApplicationArea=#Basic,#Suite;
                Description=Customized;
                SourceExpr="Sales Type";
                Visible=SalesTypeFilter = 0 }

    { 1100570001;2;Field  ;
                Name=SalesTypeCustDiscGroup;
                ToolTipML=[ENU=Specifies the sales type of the sales line discount. The sales type defines whether the sales price is for an individual customer, customer discount group, all customers, or for a campaign.;
                           SVE=Anger f”rs„ljningstypen f”r f”rs„ljningsradrabatten. F”rs„ljningstypen avg”r om f”rs„ljningspriset avser en enskild kund, en kundrabattgrupp, alla kunder eller en kampanj.];
                OptionCaptionML=[ENU=,Customer Disc. Group;
                                 SVE=,Kundrabattgr.];
                ApplicationArea=#Basic,#Suite;
                Description=Customized;
                SourceExpr="Sales Type";
                Visible=SalesTypeFilter = 1 }