Data Table From URL Definition Widget
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2016 02:56 AM
Hi all,
Using the Data Table From URL Definition widget in the Service Portal that comes with Helsinki. Cloned it so that I could make it work for me. I added the table name (cases) and added the fields I wanted to see. That however doesn't seem to be what that field means when I edit the widget. The widget defaults to 4 fields (Number,Task Type ,Short Description and Priority). I did not select all of these and actually added a couple others I wanted to see but they don't show. I love the look of the table that it presents, but it's just not acting the way I expected.I know that If I use other widget: 'Data Table From Instance Definition' it will be worked fine, but I need actually this widget because I have to pass a parameter from other widget in the URL. What am I missing about customizing/configuring a widget?
Does someone have any idea?
thanks,
Michal
מ×�×� שב×�ןמע ×�×™×§ 'שט ן קספקב×�קגץן למ×�' ×�יש×� ןכ ן ודק ×�×�יקר 'ןגעק×�: ,גש×�ש ×�×©× ×š×§ כר×�צ ןמד×�שמבק גקכןמן×�ן×�מ, ן×� 'ןךך × ×§ '×�רלקג כןמקת × ×•×� ן מקקג actually 'יש×� שצ ן צןדדןמע ×©× ×�ו×�
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2017 02:03 PM
Jesse,
In the SP we are unable to see how to set a particular view when using the Data table from URL definition widget. Can you help point us in the right direction?
Susan Williams, Lexmark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2017 02:07 PM
Furthermore, the Fields field does not seem to do what the documentation says it does: Columns to display in the table. Instead of our selected columns, we are getting the Number, then a set of 9 alphabetized columns starting with A.
Susan Williams, Lexmark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2017 12:02 PM
For what it's worth, this appears to be fixed in Jakarta patch 2. It works on my personal dev instance, but not on our instances (Jakarta patch 0).
Susan Williams, Lexmark

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2017 12:25 PM
Hey Susan,
I did some research into the fields option for data table from URL definition and here is what I found.
It looks like the option is included because we're embedding the data table widget into this one and fields is an available option for that widget.
From what I am seeing though, this option is used by data table from instance definition but URL definition is actually expected to ignore it so you might actually be hitting some odd behavior in JP2. In fact, if you look at the server script for data table from URL definition it does not ever look at the value of the fields option. You'll see that data table from instance definition does.
The intent with URL definition is that you use URL parameters (view=ess for example) to set the view for the list - not the instance options. Those really seem to only apply to data table from instance definition.
I'm going to put in a request to have our documentation updated to reflect this because it seems that the fields option should not be used in data table from URL definition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2017 01:07 PM
Jesse,
We're wanting to use this within the Service Portal. We are using the "Requests" widget to display a list of records when the user clicks the "View All Requests" link. On that page, we have simple list widgets that display the records by type (incident, change request, etc.). From the simple lists, if there are more records than our max (currently 10), the "View All" link shows in the bottom right. Clicking that link displays the list of records and this is where we are unable to impact the columns shown in our instance; however, it does appear to be working in our personal dev instance.
Ours (JP0):
Personal dev instance (JP2):
Fortunately, we already have plans to apply Patch 4 later this month, so we'll check back to see if this works after the upgrade.
Susan Williams, Lexmark