04-06-21 11:56 AM
Answered! Go to Answer.
04-06-21 01:48 PM
04-06-21 01:27 PM
04-06-21 01:48 PM
04-06-21 01:50 PM
08-02-22 09:37 PM
24-03-22 05:38 PM
Leonardo como estas?
Estoy realizando la acción de Filter collection, pero me arroja el siguiente error:
Tengo 2 colecciones, la primera es donde esta la información que quiero obtener, por medio de un dato llamado "numero_radicado"
La segunda es donde esta el numero_radicado que es con el que voy a buscar en esa colección:
Agradezco de su ayuda, para solucionar esto.
Gracias!!
------------------------------
Lina Rocio
------------------------------
24-03-22 05:42 PM
24-03-22 05:54 PM
18-05-23 11:38 AM
When filtering a collection in Blue Prism, there are certain characters that may cause issues or behave unexpectedly within the filter expressions. Here are some characters that you should be cautious about when using the filter collection action in Blue Prism:
These characters are commonly used as operators or have special meanings within filter expressions, which can lead to unexpected results or errors. To handle these characters, you can use escape sequences or alternative filter expressions, as mentioned in the previous response.
It's important to carefully consider the specific characters used in your data and adjust your filter expressions accordingly to ensure accurate and reliable filtering in Blue Prism.
01-06-23 12:03 PM
Just a warning - if your collection includes in a first column a string that resembles a date, it's possible the order of rows is changed after filtering. Issue is possibly not limited to dates only (maybe it's just the numbers, after all?), but it's the only case I know.
In my demonstration, data is in a collection called "Test" and the result collection populated by a filtering query is "Res".(See the pics.)
If the filtering query is "[A] LIKE '%2%'", the result set contains all the rows in the dataset, which is correct, but as you can see, order of rows has changed. This could have an effect to your automation, if the order of rows in relevant to your use case.
Only way to circumvent the issue (that I know), is to add a indexing to the dataset and after the filtering, order the rows again by index.
------------------------------
Mikko Kamppila
IT analyst
Kela
Europe/Helsinki
------------------------------