- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-26-2024 06:18 AM
Hi everyone.
I'm working for a client who are using remote tables.
One of these remote tables is showing data on a table extended from the task table.
On that main table is a reference field that points to the remote table.
This means everytime the record is opened, the remote table is executed and the data is retrieved.
In the outbound HTTP logs i see a lot of queries going to the endpoint that originate from text indexing.
This generates a lot of API requests, it would be nice to have text indexing active on the table, but it would be great if we could stop the text indexing from causing the remote table to be queried.
Is there a change that can be made, and what is best practice in these situations?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2024 03:04 AM
So turns out there is an attribute that can be set for each field on a table called "No text index", i set this on the field in question, and this stopped the outbound HTTP requests from happening.
There was also something for AIS (AI Search) which had a different table, but same concept which i also turned off.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2024 03:04 AM
So turns out there is an attribute that can be set for each field on a table called "No text index", i set this on the field in question, and this stopped the outbound HTTP requests from happening.
There was also something for AIS (AI Search) which had a different table, but same concept which i also turned off.