Forum Replies Created
- Posts
-
Hi
I’m also facing the same issue.
Regards
- This reply was modified 8 years, 1 month ago by .
- This reply was modified 8 years, 1 month ago by .
Thanks – that's one of the options I was going to do but I was hoping to be able to use the built in aggregate functionality – something like <%sum aggregate:field name%> that I could throw into the Results Header.
Hi,
n
We are using SharePoint 2010/SP2 and QAPPS 6.5…
n
Regards
n
Hi I’m sending you a screenshot of my qSIListForm.
For example, I want to put a fixed size between the labels and the checkboxes, because the space between them is really big. When I put ’15’ in ‘Width’ for example, it remains the same. Maybe the component has a min value and doesn’t get any smaller than that.
Thank you.
Hello,
n
n
No, I don’t think that setting can affect the grouped or the aggregate value. The body filed means the script will be invoked when rows are rendering in the front-end. For example, if you have five rows in qListView, the code in the body field will be called in every row rendering(5 times).
n
n
But on the other hand, because that code is running on the front-end, that give you a very flexible way to do your job. For your case, I think you do not need to set the body field, just add the script in the header filed for formatting the grouped/aggregated value. The script in the header will be run in one time. For example:
n
Results Header:
n
n
<script>
n
//get the field, the ‘$telerik.$’ is the jQuery object.
n
var theField = $telerik.$(‘…’);
n
//format it..
n
</script>
n
n
n
n
Hello,
n
n
I think the width of checkbox fields is working, you can check the source HTML code. I think the issue is the fields before the checkbox fields, because the width of the text is ‘auto’. Can you try to set the width for them?
n
n
n
Hello,
n
n
That works fine in my lab. Can you provide some screen-shot in qSIListView?
n
n
n
OK – thanks!
Hi ,
n
n
This is the bug of qSIListView, #420983.
n
n
As an workaround, please use export to PDF function.
n
n
n
Hi ,
n
n
The export to excel logical in qListView and qSIListView is the same with qExcelViewer. This is the same bug there. I have updated the #420983.
n
n
As an workaround, please use export to PDF function.
n
n
n
Hi ,
n
The same issue occurs in the Excel Export function for qListview and qSIListview web parts. When the column contains leading zeros – for example, 012345.9999, they are treated as number instead of text, so the leading zero is dropped (i.e. 012345.9999 becomes 12345.9999).
n
Please kindly advise if there is a workaround for this issue?
n
Thanks again!
n
n
n
Hi ,
n
Thank you! Is there a way to modify just a part of a URL defined in a web part using that qManagement web part?
n
–
Hi. I am currently trying to use these web parts in a site template and am running into the issue were when I save it as a template, with or without content, and deploy it into a new site collection the configuration inside the web parts are pointing at the old site rather than the new site.
n
So, for example, originally it was /sites/test1/ and when I create a new site /sites2/test2/ the Edit URL and New URLs and any hyperlinks that we provide for a column still has /sites/test1/
n
Any suggestions how to mitigate/solve this issue?
Hi,
n
n
That is expected. You store the site as a template with some web parts. The web parts are kept in the site, including the configuration. The configuration in the web part is fixed in the site template.
n
n
I think you can use the qManagement web part to do the modification after you restore the site. You can use this web part to search and modify other web parts.
n
n
n
Hi
n
n
It's
n
Version 6.3 (Build 2014.3.28)n
n