Dimension grayed out in qvpp extension file

[#1]

I have created an extension and would like to add 1 more dimension in the qvpp file. I have modified the qvpp file to include this dimension.

However, when I try to access this property in the client, the dropdown for the Project Stage is grayed out (in yellow) and I cannot select a dimension.

Did I miss something here ?

[#2]

Hi,

Have you checked the Definition file? you should have 2 dimensions there too

Regards

[#3]

Thank you for your response.

You mentioned 2 dimensions in the Definition.xml file. Shouldn't I just add 1 more entry instead of 2 ?

Here is the code for the Definition file. I've added 1 more Dimension. Before it used to be just 4 -

<?xml version="1.0" encoding="utf-8"?>
<ExtensionObject Label="Gantt2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Definition.xsd" Description="Display Milestones">
  <Text Initial="" Expression="Timeline"/>
  <Text Initial="" Expression="Account Name"/>
 <Dimension Initial="" />
 <Dimension Initial="" />
 <Dimension Initial="" />
 <Dimension Initial="" />
 <Dimension Initial="" />
  <Measurement Initial="" />
  <Initiate Name="Chart.BgColor.ColorHex" value="#FFFFFF" />
  <Initiate Name="Caption.Text" value="My Gantt Chart" />
</ExtensionObject>

and the code for the properties file. Added entry for Project Stage -

<div class="ToolWindow-MainBody">
    <table width="360px">
        <tr class="ToolProperty-Header">
            <td onclick="Qva.SelectToolPane(this, false)">
                Gantt Chart 
            </td>
            <th onclick="Qva.SelectToolPane(this, true)">
                <img alt="" src="unpinned.png" icon="web:unpinned" avq="img:.Chart.Title"/>
            </th>
        </tr>
        <tr>
            <td colspan="2">
                <table width="100%">
                    <colgroup>
                        <col width="130px" />
                        <col width="190px" />
                        <col width="30px" />
                    </colgroup>
     <tr>
                    <td class="ToolProperty-Literal">
                        Chart Header:
                      </td>
                      <td colspan="2">
                        <input style="width: 200px" avq="edit:.Chart.Text.0.Content" />
                      </td>  
     </tr>
     
     <tr>
                    <td class="ToolProperty-Literal">
                      Left Header:
                    </td>
                    <td colspan="2">
                      <input style="width: 200px" avq="edit:.Chart.Text.1.Content" />
                    </td>
     </tr>
     
     <tr>
                        <td class="ToolProperty-Literal">
                            Process:
                        </td>
                        <td colspan="2">
                            <input class="ToolProperty-TxtSelect" style="width:190px" readonly="readonly" avq="text:.Chart.Dimension.1.Field" /><button avq="dropdown:.Chart.Dimension.1.Field" class="ToolProperty-TxtSelectMenu" ></button>
                        </td>
                    </tr>
                    <tr>
                        <td class="ToolProperty-Literal">
                             Tasks:
                        </td>
                        <td colspan="2">
                            <input class="ToolProperty-TxtSelect" style="width:190px" readonly="readonly" avq="text:.Chart.Dimension.0.Field" /><button avq="dropdown:.Chart.Dimension.0.Field" class="ToolProperty-TxtSelectMenu" ></button>
                        </td>
                    </tr>
     <tr>
                        <td class="ToolProperty-Literal">
                            Start Date:
                        </td>
                        <td colspan="2">
                            <input class="ToolProperty-TxtSelect" style="width:190px" readonly="readonly" avq="text:.Chart.Dimension.2.Field" /><button avq="dropdown:.Chart.Dimension.2.Field" class="ToolProperty-TxtSelectMenu" ></button>
                        </td>
                    </tr>
     <tr>
                        <td class="ToolProperty-Literal">
                            End Date:
                        </td>
                        <td colspan="2">
                            <input class="ToolProperty-TxtSelect" style="width:190px" readonly="readonly" avq="text:.Chart.Dimension.3.Field" /><button avq="dropdown:.Chart.Dimension.3.Field" class="ToolProperty-TxtSelectMenu" ></button>
                        </td>
                    </tr>
          
     <tr>
                        <td class="ToolProperty-Literal">
                            Project Stage:
                        </td>
                        <td colspan="2">
                            <input class="ToolProperty-TxtSelect" style="width:190px" readonly="readonly" avq="text:.Chart.Dimension.4.Field" /><button avq="dropdown:.Chart.Dimension.4.Field" class="ToolProperty-TxtSelectMenu" ></button>
                        </td>
                    </tr>
                  
                </table>
            </td>
        </tr>
        
      <tr class="ToolProperty-Header" avq="panel::Layout.qvpp">
        <td>Layout</td>
        <th></th>
      </tr>
      <tr style="display: none">
        <td colspan="2"></td>
      </tr>
      <tr class="ToolProperty-Header" avq="panel::Caption.qvpp">
        <td>Caption</td>
        <th></th>
      </tr>
      <tr style="display: none">
        <td colspan="2"></td>
      </tr>
      <tr class="ToolProperty-Header" avq="panel::Access.qvpp">
        <td>Access</td>
        <th></th>
      </tr>
      <tr style="display: none">
        <td colspan="2"></td>
      </tr>
    </table>
</div>

[#4]

My bad.. you're right it's just one, anyway did it help?

[#5]

No it didn't. I even get a 'No Data to Display" message from the chart when I added 1 more dimension entry in the Definition.xml file.

[#6]

Hi arjhay,

Do you have any data in the QVW file you are testing the extension with?

This is an issue I ran into. My first instinct was to test my extension property pane in a blank QVW with no data and all my field picker style property panes were grayed out. Simply adding a little inline table with some sample data solved that problem immediately.

One other reason this could be happening is that you are viewing the file via the AJAX client in a browser against a QVS. In that case the properties of any  document extension object will be read only (just like any ordinary QlikView document object). However if you create a new collaboration object based on your extension object, the collaboration object's properties will be editable (just like any normal collaboration object).

Let me know if either of these solves your problem.

Regards,

Dan

[#7]

AHi Dan,

deh wrote:

Hi arjhay,

Do you have any data in the QVW file you are testing the extension with?

This is an issue I ran into. My first instinct was to test my extension property pane in a blank QVW with no data and all my field picker style property panes were grayed out. Simply adding a little inline table with some sample data solved that problem immediately.

One other reason this could be happening is that you are viewing the file via the AJAX client in a browser against a QVS. In that case the properties of any  document extension object will be read only (just like any ordinary QlikView document object). However if you create a new collaboration object based on your extension object, the collaboration object's properties will be editable (just like any normal collaboration object).

Let me know if either of these solves your problem.

Regards,

Dan

Yes, I do have data in the QVW file. And I was planning to select that dimension from the dropdown list of the extension object property but it is grayed out as I said.

I'm actually viewing the file using the QV client and not within a browser.

I did manage to figure it out. I had to modify the Script.js file and populate a new array using the dimension I need. Is this always the case when adding dimensions ? I thought you just have to add them in the qvpp properties file and definition xml file.

This action corrected the issue but the Properties sheet appearance changed from the Old view to the new view. The New view is simply a standard properties sheet. I think the application somehow disregarded my qvpp file and used a standard properties file. How was the application able to display such standard properties sheet when the qvpp file located in my extension object folder is a custom version  (see the contents of the properties file from previous email thread).

By the way, what do you mean by creating a collaboration object based on my extension object ? How do you create one ?

Thanks !

Anthony

[#8 · Accepted solution]

Hi Anthony,

Just as you can create collaboration objects based on regular QlikView objects (e.g pie charts), you can also create collaboration objects based on the extensions you write. It is not really a special feature, it's just that QlikView basically treats extension objects like any other (ordinary) QlikView object and most anything you can do with an ordinary object, you can also do with extension objects.

Also, you should not have to do anything special in your script.js to get the autopicker for dimensions to work for you. I just posted an extension on the amMap & FusionMaps Integration thread in this forum. That extension allows you to pick the dimension from the property page (i.e. the picker is not grayed-out). You might try that extension out and then take a look at my properties.qvpp and  definition.xml. This might help you tweak your extension.

-Dan

[#9]

Thanks Dan.

I'll look at it and see what I can find.

[#10]

Did you try deleting and recreating the object in the QlikView layout? QVPP changes are not reflected until the object is recreated.