reduce the amount of data returned from api call?

[jamie]

i need to drastically reduce the amount of data returned by the entity lookup api call its returning every bit of data when i am only needing a small fraction of what's being returned

Here is an example of the api call

https://www.example.com/api/v1/WorkRecord?maxSize=100&offset=0&orderBy=wrNumber&order=desc

And to be clear, i don't want to reduce the amount of records, just the data in each record, i really only need what i am displaying and the id, not every single bit of data in the record that the table is now over 100 columns, you can imagine the delays for something i can't display

yuri any thoughts on how to do this in an easy upgrade-friendly way?

[emillod]

You can use scope param to specify which fields should be returned

[jamie]

You can use the scope param to specify which fields should be returned

This is an internal espo call for when it's looking up a linked records to insert the id into the current record, what i would call a foreign key lookup, so is this something i can control inside entity defs?

[a.slyzhko]

You need to specify query param 'attributeSelect' with a list of needed attributes separated by comma. No attributeSelect means select all attributes

[jamie]

You need to specify query param 'attributeSelect' with a list of needed attributes separated by comma. No attributeSelect means select all attributes

yeah that sounds like it might be the one i'd set that in entity defs? in the links section?

"workRecords": {
"type": "hasMany",
"relationName": "cServiceSpareWorkRecord",
"foreign": "cServiceSpares",
"entity": "WorkRecord",
"audited": true,
"isCustom": true
},

[jamie]

The main issue is that when we have a one-to-one relationship, it tends to bring in an extra 20,000 PLUS records. There are situations where one-to-one relationships are necessary, but when linking one entity to another, we really don’t need to pull in every single piece of data from the foreign record—only the data required to establish the link for the current record.

Personally, this feels like a bug.

Unless yuri knows a way to limit the number of records that the entity link lookup pulls into the front end?

[yuri]

> The main issue is that when we have a one-to-one relationship, it tends to bring in an extra 20,000 PLUS records.

It's rather wrong definitions in your customization.

The initial question is clearly and correctly answered in the post #4.

[yuri]

Places in the documentation where the 'select' parameter (or its alias 'attributeSelect ') is covered:

1: https://docs.espocrm.com/development/api/crud/#list
2: https://docs.espocrm.com/development...params/#select
3: https://docs.espocrm.com/api/#/paths/Account/get

[jamie]

Places in the documentation where the 'select' parameter (or its alias 'attributeSelect ') is covered:

1: https://docs.espocrm.com/development/api/crud/#list
2: https://docs.espocrm.com/development...params/#select
3: https://docs.espocrm.com/api/#/paths/Account/get

So, what one of these do i need to do to fix my problem? What do I need to add to what file?

i need to specify exactly what gets returned when i try to link one entity to another

[yuri]

You need to specify query param 'attributeSelect' with a list of needed attributes separated by comma. No attributeSelect means select all attributes

Query parameter. Query parameter is parameter specified in the URL, the way you already specified some (e.g. maxSize). a.slyzhko clearly stated what to do. Specify the attributes you need in query parameters, the attributes are separated by comma. Attributes correspond to the field names. It's all covered in the docs.