Announcement

**Isomorphic** · 21 Oct 2015, 09:30

Since the expansion record is potentially based on the data inside the record that has been updated, and in ways the framework cannot always anticipate (since getExpansionComponent() is an override point), it makes sense to automatically discard the existing expansion component when a record is updated. If it makes sense to do so in your app, you can re-expand it via expandRecord().

**trainot** · 21 Oct 2015, 23:48

Hi Isomorphic,

I understand your point of view, however the program takes decisions by itself based on potential, non-verifiable facts. We are the owner of the data and we would prefer to take this decision by ourselves. Is there a way for you to give us the choice of when to collapse a record in the context above?

Thank you in advance

**Isomorphic** · 22 Oct 2015, 10:11

See previous post: it seems like you may have missed that you can re-expand programmatically.

**trainot** · 22 Oct 2015, 23:43

Hi

I did not miss the fact that I can expand programmatically. This is an obvious fact. A programmatic expand also retrieves data from the server, additionally users can see clearly that the record is closed and then expanded. I thought these disadvantages were clear. Let me reiterate that i am the data owner and i prefer to take this decision when to collapse the record. If it is possible to have this flexibility, great.

Thanks

**Isomorphic** · 26 Oct 2015, 12:24

Looking back at this, there are some basic issues with your code:

1. you set the operationType on the DSRequest object. It's expected on the DSResponse

2. you're re-using a DSResponse from a fetch operation. You should be creating a new DSResponse, as the DSResponse from the fetch operation potentially has a lot of settings on it, as well as internal state maintained by the framework, which don't make sense with updateCaches().

It looks like these kinds of issues could cause collapsing of records which don't need to be collapsed (the framework is actually selective about whether collapse is performed), so correcting them might prevent the collapse that you don't want - we can't tell definitively because you've never shared your settings and/or code for the expansion modes you're using.

**trainot** · 28 Oct 2015, 03:28

I am glad to find out that records should not be collapsed on updateCaches(), changed according to your suggestions:

try {
final Criteria criteria = new Criteria(
"schedule_id", designElementsInstance.preparationsGrid.getSelectedRecord()
.getAttribute("SCHEDULE_ID"));
final DSRequest dsRequest = new DSRequest();
dsRequest.setOperationType(DSOperationType.FETCH);
dsRequest.setOperationId("fetch_id");

DataSource.get("disseminationPrepDS")
.fetchData(criteria, new DSCallback() {
@Override
public void execute(
final DSResponse response,
final Object rawData,
final DSRequest request) {
DSResponse updateResponse = new DSResponse();
updateResponse.setOperationType(DSOperationType.UPDATE);
ListGridRecord updateRecord = new ListGridRecord(response.getData()[0].getJsObj());
updateResponse.setData(updateRecord);

DataSource.get(
"disseminationPrepDS")
.updateCaches(updateResponse, request);
}
}, dsRequest);

The UPDATE operationType is set on DSResponse and i set the data of the response to the original response, which requires an (array of) ListGridRecord instead of Record. updateRecord contains the proper data, that has been verified by me, and we are always sure that the fetched data contains only one record.
However in this case updateCaches does not work, meaning it does not update the selected grid record, with no error messages whatsoever. Could you check why updateCaches does not work for this case ?
Thank you

**trainot** · 28 Oct 2015, 07:55

Adding the line :
request.setOperationType(DSOperationType.UPDATE);

to the above causes updateCaches() to work, but the record is again collapsed. Note that I created the DSResponse from scratch. Grateful for a solution for this.
Thanks in advance

**Isomorphic** · 28 Oct 2015, 11:31

The second argument to updateCaches() (a DSRequest) is not required. However, if you do pass a request, you definitely do not want to pass a dsRequest that says it is a "fetch" whereas the response says "update", as this makes no sense.

You also don't want to be re-using a request that has actually executed, as previously covered for the response argument.

**trainot** · 29 Oct 2015, 00:53

If I don't need to use the request for updateCaches(), updateCaches() will work but the record is again collapsed:

final Criteria criteria = new Criteria(
"schedule_id", designElementsInstance.preparationsGrid.getSelectedRecord()
.getAttribute("SCHEDULE_ID"));
final DSRequest dsRequest = new DSRequest();
dsRequest.setOperationType(DSOperationType.FETCH);
dsRequest.setOperationId("fetch_id");

DataSource.get("disseminationPrepDS")
.fetchData(criteria, new DSCallback() {
@Override
public void execute(
final DSResponse response,
final Object rawData,
final DSRequest request) {
DSResponse updateResponse = new DSResponse();
updateResponse.setOperationType(DSOperationType.UPDATE);
ListGridRecord updateRecord = new ListGridRecord(response.getData()[0].getJsObj());

updateResponse.setData(updateRecord);

DataSource.get(
"disseminationPrepDS")
.updateCaches(updateResponse);

}
}, dsRequest);

The above makes updateCaches() work, but the record is collapsed automatically. Again note that I create DSResponse from scratch, as suggested by you. Grateful for any solution which will make the record not collapse.
Thank you

Announcement

DataSource updateCaches() automatically collapses expanded record

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment