Where in URL works in some cases

Support
1

Hi,

Does anyone know why the where in a URL works when asking for JSon but not for CSV data?

This works:
https://www.ragic.com/myragicsolutions/mtime/4.csv?APIKey=…&where=1001062,eq,Yes

But this does not:
https://www.ragic.com/myragicsolutions/mtime/4?api&APIKey=…&where=1001062,eq,Yes

Thanks

2

They should work, we will probably need to see the actual call to find out why it didn’t.

3

Hi,

I recreated the problem in the RagicSolutions Demo DB

This brings back 2 records which is correct:
https://www.ragic.com/RSDemo/ragicnew-tab/10002?api&APIKey=c1BaY1RLcEsxYzRUanNDWkcxSkpQUy93SU9wVTJCalNVOWJNTFRzQThmTjNtVlJmMGgrdWZMM3grcnBMK2ZRckZIMnNLV1l2bmRrPQ==&where=1000103,eq,Yes

This downloads all 3 records which is not correct:
https://www.ragic.com/RSDemo/ragicnew-tab/10002.csv?APIKey=c1BaY1RLcEsxYzRUanNDWkcxSkpQUy93SU9wVTJCalNVOWJNTFRzQThmTjNtVlJmMGgrdWZMM3grcnBMK2ZRckZIMnNLV1l2bmRrPQ==&where=1000103,eq,Yes

I hope this helps the developers.

Regards

4

Hi,

We are releasing and app that makes these calls to Ragic and with this not working this is causing a lot of traffic and also processing both on the Ragic side and on the customer side.

Please can someone look into this ASAP.

Thanks

5

Hi,

Any news on this?
Here are more examples form the Demo DB, I can’t share the live links and API Keys but you will see the issue using these links.
https://www.ragic.com/RSDemo/ragicnew-tab/10002?api&APIKey=RERyOUlTVjBLVWkwMy9kNElNYThMaXVhTWYvQW5RYzFaYTFlZUZqMUw3OGNDWlFGR002MDhNUWp3N2RERFpoZUFwZGl2dW96TXBFPQ==&listing&where=2000463,eq,E-00002
returns one record which is correct
https://www.ragic.com/RSDemo/ragicnew-tab/10002.csv?APIKey=RERyOUlTVjBLVWkwMy9kNElNYThMaXVhTWYvQW5RYzFaYTFlZUZqMUw3OGNDWlFGR002MDhNUWp3N2RERFpoZUFwZGl2dW96TXBFPQ==&listing&where=2000463,eq,E-00002
returns all the records.

Kind regards

6

Hi,

Support and development this is not affecting two clients please can this be looked at urgently.

Thanks

7

My apologies, not sure why I always missed this post.

The reason is pretty simple, where clause is only supported on our API, not on CSV URLs. CSV URL is not part of our API, I believe they are only generated when you do a publish to the web. They actually don’t support any of the HTTP API parameters.

It might be something that we can support in the future, but that will require a whole implementation of the where parameters. This is not bug that we can just fix, it’s just not supported yet and where parameters are not processed at all for CSV downloads.