• State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 6290 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

Creating a foreign key (FK) to a custom view

robin.olivier
over 7 years ago

Hello !

In v6, it was possible (using the Schema Extension utility) to create a column containing a foreign key pointing to a custom view.

In v8, custom views (and custom union views for that matter) don't appear in the dropdown list when I'm trying to add a FK column in new a table.

Is there a reason this is not possible anymore ? Does anyone has a solution to this ?

 

This a is big problem for us so any help will be greatly appreciated !

Regards,

v8 :                                                                                   v6 : (FAU_hierarchy_commodity is a custom view)

                         

  • 0 over 7 years ago

    In short, it was a glitch of version 6 that this was even possible. The created FK didn't work in regards to relational integrity (DC/DS etc.).

    Starting with 7 we removed the ability to create such incomplete FK relations at all.

    If you need further information I suggest you contact support.

  • 0 over 7 years ago
    Hello Markus!

    Thanks for this information.
    This is quite unfortunate for us as we were using this "feature" a lot... Was the fact that this feature was in fact a bug documented anywhere?

    We are trying to find alternative solutions. We seem to have found a possible workaround with the dynamic foreign keys. Indeed, when creating a DynFK using the Schema Extension utility, we seem to be able to select views and union views as the target for the DynFK.
    Do you know if this is a feature that we can expect to be kept in the future, or is it also a bug that may be removed at any time?
    Also, do you have any advice/warning/other remarks on using DynFK to solve our problem? Does it seem a good idea to you? We're quite blind here, as this is a new feature and we don't really know how it works...

    Thanks again for the help !
  • 0 over 7 years ago
    The DynFK is not a new concept and existed in V6 as well. The dynamic FKs are fundamental to the product, so currently I see no reason why this should be removed.

    If you need any further assistance feel free to contact support and subscribe your use-case in detail.

    Thank you
  • 0 over 7 years ago
    Hello again Markus,

    I did contact support and created a Service Request last week: my case is still being investigated at the moment. I'm using the Forum to try to get some additional info, that's all.

    Thanks for the information regarding DynFKs. I never noticed them in v6 (v6.1.2 to be precise... maybe they were added in 6.1.3 or 6.1.4!).
    I've got no doubt that the feature of the DynFKs itself will not be removed, my concern was more related to DynFKs pointing to views or union views specifically.

    Regards,
  • 0 over 7 years ago
    Dynamic foreign keys are part of the product since version 4.1. You should have seen them in the assignment resources, delegation and system role assignments to give you some examples.

    With version 7 with intensified the usage of those keys and make them more usable for customizations.