• State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 9913 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enable or disable columns on MasterData forms

acoromi
over 7 years ago

Hi all.

I'm not sure if this is possible, but i will appreciate any clarification about it.

I use the unsaccountb table to store accounts from two different systems. I've extended the unsaccountb schema to allocate a few new columns that are needed to store some information. Let's imagine that i have 3 custom columns: column1, column2 and column3, where column1 and column2 are related to system1, and column3 is related to system2.

The problem is that when I login into Manager, and I select one account for, let's say, system1, the Manager shows me all THREE custom fields on the "custom" tab, when actually only two of them are related to this account (of system1). This behaviour is generating some confusion in my customer.

Is there some way to "hide" the fileds depending on the account's system that is being edited?

Yes, I know that I can use templates to manage this situation more or less efficiently, but in this case I think that my first approach (if possible) is better.

 

Thank you!

  • 0 over 7 years ago
    Hi acoromi

    Using the manager, the objects of the UNSAccountB table are represented using the view UNSAccount. Using Designer, you can do the following steps:
    Go into the UNSAccount-View (Table) Definition in the database schema section. On the columns, you can now define a so called "Column Group". If you name the Column Group exactly like the according UNSRoot of the objects, this will result in the following behaviour:

    Looking up the master data form of a object in UNSRoot <A> will display an additional tab named <A> covering all attributes being assigned to column group <A>, but will hide all attributes being assigned to column group <B>.

    Looking up the master data form of a object in UNSRoot <B> will display an additional tab named <B> covering all attributes being assigned to column group <B>, but will hide all attributes being assigned to column group <A>.

    But be careful to use the exact names of the UNSRoots you've defined for your custom defined systems. And keep in mind: the objects are stored in UNSAccountB, the objects being displayed are UNSAccount.

    HTH
    Carsten
  • 0 over 7 years ago
    Hi, Carsten.

    Sorry, but I'm a bit lost with your reply. Let me explain.

    I open Designer, go to Identity Manager Schema, click on Type:Proxy node, select UNSAccount table and on the central panel now I select "UNSAccount". This opens the "Table properties" on the lower half of the screen. Well, and then?? What should I do now??

    There is a tab named "ViewAddons" where it seems that I can specify a new view, and another tab named "Multicolumn uniqueness" where it seems that I can define some sort of new Unique Keys for the view.

    Please, could you help me further?

    As a side note, my customs fileds are defined in UNSAccountB. They doesn't appear in UNSAccount. Is this correct??

    Thanks!!
  • 0 over 7 years ago
    Hi acoromi

    Ok, let's just clarify some things: what version of Q1IM are you using: 6.x or 7.x?
    When you're in the table properties, you should see a list of columns in the above window which are tight to the table. Correct?

    HTH
    Carsten
  • 0 over 7 years ago
    Could this nice feature be applied to other tables i.e. ADSAccount or only to UNSAccount?
    Thanks!
  • +1 over 7 years ago
    Hey xd

    This a default feature being available for each and every table of 1IM. Using the column group attribute for custom attributes on default tables will establish the column group as a new tab on the dedicated master data form.

    The only speciality is for UNSAccountB where the tab name will be applied following the name of the UNSRoot to hide attributes that do belong to other custom target systems being established in other UNSRoot.

    HTH
    Carsten
  • 0 over 7 years ago
    Carsten,

    Thank you so much for the details.

    Cheers!
  • 0 over 7 years ago
    Carsten, it's 7.1.1

    Reading your reply to xd user has helped me a lot, and finally I've found it!

    One last question. Could it be possible to specify more than one group per column? Then, I could reuse the same column for differents UNSRoots.

    Thank you!!
  • +1 over 7 years ago
    You are able to specify more than one by separating them with a comma ,
  • 0 over 7 years ago
    oops... I'm dumb. It was an obvious answer. Sorry.

    Yes, it works.

    Thanks a lot.