Query Entity Data giving error

Getting an error while running the Query Entity Data in Data Service of Uipath , from Uipath Studio:
The version of Data Service Activity package is 21.10.1, Uipath Studio Version is : 2022.4.1
The query i am execution is : ‘Keyword’ field in data service ‘is in’ a , then return all rows. If i just use ‘Keyword’ = in the Query panel of the Query Entity Data ,then it works fine.

Please let me know of any pointers in solving the error message.

Below is the error message:

RemoteException wrapping UiPath.DataService.Activities.Exceptions.EntityServiceException: Error: Internal Server Error, TraceId: 294bdda1e483a449bac6a4378c90187e
at UiPath.DataService.Activities.Extensions.HttpClientExtensions.d__101.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.DataService.Activities.Extensions.HttpClientExtensions.<ExtractResponseAsync>d__81.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.DataService.Activities.Extensions.HttpClientExtensions.d__41.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.DataService.Activities.Services.EntityService.<QueryEntityDataAsync>d__121.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.DataService.Activities.QueryEntityRecords1.<GetEntityDataAsync>d__39.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.DataService.Activities.QueryEntityRecords1.d__38.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.DataService.Activities.BaseEntityActivity.<>c__DisplayClass15_0.<b__0>d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.DataService.Shared.Telemetry.TelemetryService.d__7`1.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.DataService.Activities.BaseEntityActivity.d__15.MoveNext()
— End of stack trace from previous location where exception was thrown —
at UiPath.Shared.Activities.AsyncTaskCodeActivityImplementation.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at UiPath.Shared.Activities.ContinuableAsyncCodeActivity.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

Can you please clarify this a bit more? The query is failing with the ‘is in’ operator and working fine with ‘=’ keyword?

Also, can you please share the type of column for ‘Keyword’? And how many/what are the values being passed when it fails? (Please DM me the details if you cannot share here)

We will start looking at this issue on the backend.

Yes getting an error if used ‘is in’ in the Query Panel of Query Entity Data. But if i use = to match with a single string value not getting any error. But i need all rows that match against a list of strings, that is where it is failing.

‘Keywords’ is a text column in the Entity.If i match '‘Keywords’ column with ‘is in’ operator against a List of Strings, getting the error.

Thanks @mailsmithash.

At first look at traces, it looks like we have have an issue on the backend. The engineering team is going to look at it. Can you please share the list of strings your are passing to the query or a sample of it? That generally helps with debugging faster.

If ‘=’ operator is working fine, you can work around this by setting the conditions operator to ‘Any (OR)’ and then adding each string as a separate condition.
image

And if you need multiple conditions, you can create a Group with OR and keep the overall conditions as AND -
image

Was able to run it successfully now,

  1. if the datatable read from Excel file has empty columns in it and it is coverted to list.
  2. This list is passed onto the ‘is in’ condition it was failing.
  3. Used Filter Datatable to remove empty rows in a column.
  4. Then converted the Datatable column to a list.
  5. Now using ‘is in’ is working.
  6. Had selected A1:A212, though there were only 12 rows in a single column, the datatable had empty rows in the column, which was causing this issue when converted to list.

Hope this is useful. Thanks

Below are the screen shots.

1 Like

Thank you so much for the input and helping identify that this issue happens when one of the inputs in the list is blank or empty. We will make sure to get this correctly fixed on the backend as well!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.