• State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 94 subscribers
  • Views 3930 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

Sync editor is neither picking custom column group nor allowing me to create one if the target system has more than 1 primary keys in a table

Pradeep Pola
over 7 years ago

Sync editor is neither picking custom column group nor allowing me to create one  if the target system has more than 1 primary keys a table

 

oneIM Version 7.1

target DB-MSSQL SERVER

  • 0 over 7 years ago
    Hi Pradeep,

    Can you please clarify what you're trying to accomplish here? Have you extended the schema and now you're not seeing the changes in the sync editor?

    Perhaps you just need to update the schema?

    Trevor
  • 0 over 7 years ago

    Hi Trevor,

    I actually created a sync project between UNSAccountB and sqltable , where the target sql table has 3 primary keys , where the combination of 3 attributes is unique.

    In General Sync Editor Gives creates a Virtual Column Group(which is a combination of all three primary keys) automatically but in my Scenario, it is not creating one.

    Due to this, i am unable to browse the data , when i click on browse and select one object it just throws an error stating more than one object returned.

     

    I did try update schema but no use

  • 0 over 7 years ago
    Are the columns marked as primary key columns in the MSSQL database or are they just meant to be unique?
  • 0 over 7 years ago
    Columns are marked as primary key and all PK columns are tagged to unique index
  • 0 over 7 years ago
    I've checked but I am unable to find some related known bug. So please contact support to help you out.
  • 0 over 7 years ago

    Just to share the cause and the solution to this issue.

    Cause

    If more than one table has a unique index defined with the SAME name, the connector wasn't creating a column group as the primary key.

    Solution

    Please contact support and request the HotFix for VPR#29856 for this issue.