<?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 Re: What is Collaborative Object? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/What-is-Collaborative-Object/m-p/1227613#M869072</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess they are talking about Server Objects or Shared Objects or whatever other name is assigned to objects created by end-users in the AccessPoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Those objects have one major issue: by default, in the AccessPoint there is no information available about fields and their content. Also, the table viewer that shows you the data model in the current document is only available in QV Desktop. The best a developer can do is to give fields a descriptive name, but that goes only so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's why I think adding real Metadata to the fields that can be used to create Server Objects and expressions is a real life-saver for end-users.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 Nov 2016 08:01:05 GMT</pubDate>
    <dc:creator>Peter_Cammaert</dc:creator>
    <dc:date>2016-11-25T08:01:05Z</dc:date>
    <item>
      <title>What is Collaborative Object?</title>
      <link>https://community.qlik.com/t5/QlikView/What-is-Collaborative-Object/m-p/1227612#M869071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While practicing examination for Qlikview Developer, I got the following question:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which technique should a developer use to clearly describe dimensions and measures for end users who need to use &lt;SPAN style="color: #ff0000;"&gt;collaborative objects&lt;/SPAN&gt;?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A. Add field Metadata tags to fielkds in the load script&lt;/P&gt;&lt;P&gt;b, put a How To sheet in the application&lt;/P&gt;&lt;P&gt;C. put descriptive information in each object's help text&lt;/P&gt;&lt;P&gt;D. Add a system table to the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Answer:A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But does anyone what is Collaborative Objects?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a billion!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/What-is-Collaborative-Object/m-p/1227612#M869071</guid>
      <dc:creator />
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: What is Collaborative Object?</title>
      <link>https://community.qlik.com/t5/QlikView/What-is-Collaborative-Object/m-p/1227613#M869072</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess they are talking about Server Objects or Shared Objects or whatever other name is assigned to objects created by end-users in the AccessPoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Those objects have one major issue: by default, in the AccessPoint there is no information available about fields and their content. Also, the table viewer that shows you the data model in the current document is only available in QV Desktop. The best a developer can do is to give fields a descriptive name, but that goes only so far.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's why I think adding real Metadata to the fields that can be used to create Server Objects and expressions is a real life-saver for end-users.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Nov 2016 08:01:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/What-is-Collaborative-Object/m-p/1227613#M869072</guid>
      <dc:creator>Peter_Cammaert</dc:creator>
      <dc:date>2016-11-25T08:01:05Z</dc:date>
    </item>
  </channel>
</rss>

