Options
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 15 subscribers
  • Views 96 views
  • Users 0 members are here
Related

Creating object using Connection to External Database

gronwmi

I have a "Vendor" object that is created/edited/deleted through a Connection to External Database. This has been working very well. I am now in need of this "Vendor" object to both be created manually, as well as the existing Connection to External Database. Is this possible?

My concern is that I do not want any manually created Vendor objects to update the external data source. I want both the manually created "Vendor" objects to exist in M-Files without impacting any of the "Vendor" objects created by the Connection to External Database. 

As well, I do not want the Connection to External Database to delete any of the existing "Vendor" objects that were created manually in M-Files, and are not present on the import.

  • 0

    That cannot be done unless you go through a rather complicated process of inserting a separate external database in between you external source and M-Files. This separate database will need 2 tables, 1 that has a one way incoming connection from the external source, and one that has a one way incoming connection from M-Files. On top of that you will need to create a View in the new database that merges data from those 2 tables to provide a new source for your object type in M-Files. In M-files you need to configure Update, Insert and Delete statements to connect to the second table while the original Select statement must connect to the View with the merged list.
    All in all it gets so complicated and error prone that I strongly advice against going down this road!
    Laminin Solutions https://lamininsolutions.com/ have developed an SQL Connector that might be able to help you do this. I am not certain about its capabilities in this scenario, but give them a shout to find out.

  • 0

    As already mentioned this is not possible: when you configure an external object type with the connection to an external database, that database becomes the master data source and all objects in that object type need to exist in the database. It's not possible to create objects that are only internal to M-Files in that same object type.

  • 0

    Should roughly look like this. I'd go and edit existing records from external source tho... Or, a VAF/Web Service connection could you make have only one Vendor Object and keep it simple for user while making it complicated for admins... 

M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.