Problem adding action group in page extension on page 20 (365 BC Spring 2019)

sander7sander7 Member Posts: 10
Hi all,

I'm having some issues with adding actions to my page extension on page 20.
By request from MS i have to either use addfirst or addlast, which both take an anchor name as parameter.
Theese are the existing actions on page 20
zm8kr68x941h.png

I wan't to add my actions in a new group last in actiongroup called <Action57> (Functions).
However the compiler in VS Code tells me that the action 'Action57' is not found in the target.
I have tried to include the < and >, with and without " around, but no luck

If i pass the value IncommingDocument into addlast it compiles just fine, but that is not where my actiongroup should be.

Does anyone have an idea how i can have my actiongroup added where i wish?
Is it because the Name property of the ActionGroup has not been defined by MS?
And if that is the case, why can i add fields to the repeater, also using addlast with the parameter of an "unnamed" control?

Any input are more than velcome. :-)

TIA

// Alexander

Regards,

Alexander Pallesen
Freelance Navision Developer

Comments

  • KlappspatenKlappspaten Member Posts: 22
    edited 2019-10-09
    To identify the problem, have you tried adding your customization after ActionGroup IncomingDocument? If this is possible, I assume that there is a problem with the naming done by Microsoft.
  • sander7sander7 Member Posts: 10
    edited 2019-10-09
    Yes. Making an addlast with IncommingDocuments as parameter works fine as stated..
    Regards,

    Alexander Pallesen
    Freelance Navision Developer
  • NAVAaronNAVAaron Member Posts: 7
    w01gwb439ejf.png

    Intellisense shows the available Actiongroups. AL is using the english Captions (for whichever reason i don't know)
    So you should use
    addlast("F&unctions")

    Regards,
    Aaron
  • sander7sander7 Member Posts: 10
    Thx Aaron,

    Works like a charm. :)

    Regards
    Alexander
    Regards,

    Alexander Pallesen
    Freelance Navision Developer
Sign In or Register to comment.