<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Non-Unique User Names in SQL ODBC UDC Connector in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Non-Unique-User-Names-in-SQL-ODBC-UDC-Connector/m-p/1600068#M14087</link>
    <description>&lt;P&gt;&lt;SPAN&gt;We have an SQL-based ODBC user directory connector. The usernames being returned from this user directory connector is non-unique. The same username may be used by two different users. We expected, based on the documentation, that this was supported via the unique ID field in the table definitions. However, when we sync users, users are merged based on username, so only one user record is added in the QMC for each username, even if there are multiple users with different distinct ID fields for that same user. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Does anyone&amp;nbsp;know how to get this to work for our user case where usernames are not unique. In the ODBC example, it says "If the user IDs are unique, the ID column is redundant.", which is not our case &lt;A href="http://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/ODBC-example.htm" target="_blank" rel="noopener"&gt;http://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/ODBC-example.htm&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is an example of two user records with the same username as returned from the "User" table (view) query.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Users Query Result.PNG" style="width: 340px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/15094i46DAA075DF398BA4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Users Query Result.PNG" alt="Users Query Result.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Here are attributes for those users and the resulting user records as shown in the QMC.&amp;nbsp; User records are merged, which is not what we want.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Attribute Query Result.PNG" style="width: 989px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/15095i3DF5C585E1E65C93/image-size/large?v=v2&amp;amp;px=999" role="button" title="Attribute Query Result.PNG" alt="Attribute Query Result.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 05:21:24 GMT</pubDate>
    <dc:creator>pleiker44</dc:creator>
    <dc:date>2024-11-16T05:21:24Z</dc:date>
    <item>
      <title>Non-Unique User Names in SQL ODBC UDC Connector</title>
      <link>https://community.qlik.com/t5/Management-Governance/Non-Unique-User-Names-in-SQL-ODBC-UDC-Connector/m-p/1600068#M14087</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We have an SQL-based ODBC user directory connector. The usernames being returned from this user directory connector is non-unique. The same username may be used by two different users. We expected, based on the documentation, that this was supported via the unique ID field in the table definitions. However, when we sync users, users are merged based on username, so only one user record is added in the QMC for each username, even if there are multiple users with different distinct ID fields for that same user. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Does anyone&amp;nbsp;know how to get this to work for our user case where usernames are not unique. In the ODBC example, it says "If the user IDs are unique, the ID column is redundant.", which is not our case &lt;A href="http://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/ODBC-example.htm" target="_blank" rel="noopener"&gt;http://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/ODBC-example.htm&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is an example of two user records with the same username as returned from the "User" table (view) query.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Users Query Result.PNG" style="width: 340px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/15094i46DAA075DF398BA4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Users Query Result.PNG" alt="Users Query Result.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Here are attributes for those users and the resulting user records as shown in the QMC.&amp;nbsp; User records are merged, which is not what we want.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Attribute Query Result.PNG" style="width: 989px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/15095i3DF5C585E1E65C93/image-size/large?v=v2&amp;amp;px=999" role="button" title="Attribute Query Result.PNG" alt="Attribute Query Result.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 05:21:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Non-Unique-User-Names-in-SQL-ODBC-UDC-Connector/m-p/1600068#M14087</guid>
      <dc:creator>pleiker44</dc:creator>
      <dc:date>2024-11-16T05:21:24Z</dc:date>
    </item>
  </channel>
</rss>

