Hide a Tab on a Form

fmhigue
fmhigue Member Posts: 290
edited 2007-05-04 in NAV/Navision Classic Client
I got Item Card Form. It contains multiple Tabs but for a new company policy I will hide Invoicing Tab and Vendor Tab.

How can I do that?
I got History & Security Granule but it only hide fields.

Thank you
Paco

Comments

  • nunomaia
    nunomaia Member Posts: 1,153
    You need to go form designer and change form layout.
    To have access to form designer you must have a license.
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • fmhigue
    fmhigue Member Posts: 290
    Nunomaia I got the license to do it, but the Tabs must be hide based on Roles.
  • nunomaia
    nunomaia Member Posts: 1,153
    Std. Navision doesn’t allow that.
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • nunomaia
    nunomaia Member Posts: 1,153
    A workaround it’s to use a form for each role.
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • David_Singleton
    David_Singleton Member Posts: 5,479
    fmhigue wrote:
    I got Item Card Form. It contains multiple Tabs but for a new company policy I will hide Invoicing Tab and Vendor Tab.

    How can I do that?
    I got History & Security Granule but it only hide fields.

    Thank you
    Paco

    The only way to do this, is to create the tabs yourself in code. Its not very difficult, but it is quite time consuming. I think if you explain how much it will cost, then the client is more likely to just want to do it the standard Navision way.
    David Singleton
  • DenSter
    DenSter Member Posts: 8,307
    I'd like to see you explain how to create tabs in code. I don't think that property is accessible in C/AL code.
    Daniel Rimmelzwaan
    RIS Plus, LLC
  • David_Singleton
    David_Singleton Member Posts: 5,479
    DenSter wrote:
    I'd like to see you explain how to create tabs in code. I don't think that property is accessible in C/AL code.

    Code wise its pretty simple, but very time consuming.

    Basically take form 330 from an old version (say Navision 2.01) and move the buttons to the top of the page. Then use the logic in form 330 from a later version (say 3.70) to decide which button to show, and to then move the visible ones so they touch each other across the top. These are now basically your Tabs.

    Now take form 5113 and follow the way they move frames around to build the actual tab sections.

    In the end the Form is almost the same as a normal Navision tab, the biggest issue is that Ctrl+Page Up/Down don't work.

    I have a couple somewhere, but I would need to restore some databases and do some searching. But anyway its more fun if you do it your self.
    David Singleton
  • jonsan21
    jonsan21 Member Posts: 118
    What an idea!! :D
    Rgds,

    Jon.
  • DenSter
    DenSter Member Posts: 8,307
    Right so it's not tabs but something that looks like tabs.
    Daniel Rimmelzwaan
    RIS Plus, LLC
  • David_Singleton
    David_Singleton Member Posts: 5,479
    DenSter wrote:
    Right so it's not tabs but something that looks like tabs.

    If it Quacks like a duck and swims like a duck... you know the rest.

    By the way, I would not normally implement this. I use it more to show users that it can be done, but that the end result is not ideal, and definitely not cost effective. I have whole lot of "you shouldn't do this" 's that I use specifically just to show the client the proper way to do it.

    By the way, not sure if you know it, but in ver. 1.4 they had redesigned option strings, so instead of entering " Account G/L,Item,Resource" you would enter:
    0::""
    1::Account G/L
    2::Item
    3::Resource.

    Any item you left out would still appeared code wise and internally, as an integer, but the text would not display, or in the TAB case, the tab would be there but invisible. But for some reason when 1.4 was released as 2.00 this feature vanished. Never to return again.
    David Singleton
  • AS
    AS Member Posts: 3
    edited - sorry - my suggestion was irrelevant

Categories