Announcement

**Isomorphic** · 28 Jan 2013, 11:51

We're not 100% clear on what you're attempting to achieve but it sounds like you're taking an approach that is going to be difficult to support.

If you issue a fetchData() request on a grid, the following steps occur:
- a ResultSet instance is created automatically and assigned to the grid as this.data.
- the grid attempts to "get" the set of rows to be displayed, which causes the ResultSet to issue a dataSource fetch request, using the criteria and callback you supplied.
- The callback will fire when the fetch request completes.
dsResponse.data will contain the data returned by the server (raw-records).

The response would not contain a direct pointer to the resultSet instance as you seem to be expecting. You could get at it by looking at the listGrid's "data" object, but attempting to manipulate it directly may be difficult.

--
If your goal is to perform a dataSource fetch, manipulate the returned results in some way, and populate the grid with them, it's easiest to do this without ever using a ResultSet or performing a dataBoundComponent fetchData() call.
Instead you can call DataSource.fetchData(), and in the callback, manipulate the dsResponse.data array as you need, then assign it to the grid via a simple setData() call.

Having said that, we are not clear on your use case, so if this won't work for you, please try to describe exactly what you're trying to achieve at a high level so we have a better idea of what you're doing.

**RickBollinger** · 28 Jan 2013, 12:30

A very quick reply on a complicated goal. I am going for the following 'use case' presentation with grids.

Code:

+topic 1  (issues 1-8 unexpanded)
+topic 2  (issues 9-10 unexpanded)
-topic 3
          +issue 11 (tasks unexpanded)
          +issue 12 (tasks unexpanded)
          +issue 13 (tasks unexpanded)
          -issue 14
                -task 23
                -task 24
                -task 25
                -task 26
          +issue 15 (tasks unexpanded)
          +issue 16 (tasks unexpanded)
+topic 4  (issues unexpanded)
+topic 5  (issues unexpanded)

Actually, I had this structure working. I did it by using expansionRelated stuff. I created the task grids using expansionRelatedProperties from the listgrid above. There actually IS one related relation. Tasks each have an IssueID for the issue that owns them.

This let me click around, but it was missing a number of elements I really need.

1) the issues are not really 'related' to topics. The topics contain fields that make up criteria to select issues. (That's why I was doing the Issue.fetchData.)

2) issues 'found' by criteria in topic 1 should not be duplicated under topic 2 or any other later topic.

3) as an added complication, a recordDoubleClick on an issue or task should open an appropriate window.

I may have been close. I did see the returned data: "Array[9]". I guess as long as I am in the callback function, I can removeAt() the duplicate records without having to make a copy.

Code:

Instead you can call DataSource.fetchData(), and in the callback, manipulate the dsResponse.data array as you need, then assign it to the grid via a simple setData() call.

I will try to make this change and see what blows up!

Thanks,

Rick

**RickBollinger** · 31 Jan 2013, 07:55

I am revising my approach. However, I hit a bump. Before I assign issues to topics, I need to have all the issues for the particular project assembled in one place. I thought cacheAllData would give me a synchronous result. When I check hasAllData it is false. The call is below.

Code:

Issue.getClientOnlyDataSource( { ProjectID: Application.currentProjectID },
    function (dataSource) {
        Log.logDebug("************ project issue records fetched: " + this.echo(dataSource));
        if (dataSource.hasAllData()) {
            if (dataSource.cacheData.getLenth() > 0) {
                Log.logDebug("************ done with successful MeetingTopic.fetchData call with recordcount"  );
            } else {
                isc.say("No project issue records fetched for ProjectID: " + Application.currentProjectID);
            }   // end if (dataSource.cacheData.getLenth() > 0)
        } else {
            isc.say("Error: dataSource.hasAllData() is not true fetching project issue records for ProjectID: " + Application.currentProjectID);
        }
    }, // end of Issue.getClientOnlyDataSource function
    {   showPrompt: true }, // requestProperties
    {   ID: "ProjectIssue", addGlobal: true, cacheAllData: true }  // dataSourceProperties
);  // end of Issue.getClientOnlyDataSource call

How can I force hasAllData to be true? Do I need to loop or delay or something?

Rick

**RickBollinger** · 31 Jan 2013, 08:51

This post can be ignored. I don't need a synchronous result. That would be too difficult, anyway.

Rick

Announcement

dsRequest.resultSet is undefined

Comment

Comment

Comment

Comment