Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
SOLVED
Hello experts!
I'm currently in the process of building API endpoints through Alteryx. I have managed to do that where I'm basically using the Download Tool and JSON Tool. After this, I'm filtering the JSON Name by CrossTab (each record has a number 0,0,0,1,1,1,2,2,2, so I'm basically grouping them based on the duplicate integers)
However, here is the catch: When I add a second endpoint, the JSON Name goes from 0,0,0,1,1,1,2,2,2 and then back to 0,0,0,1,1,1 which is fine (it is behaving as it should), but my issue is that when I want to use the CrossTab it only takes the unique records, so the second endpoint is not being transformed by the CrossTab.
Ideally what I would like is that it compares if that number already exists, if it does then just continue from the last highest record, so in this example it should not go from 2,2,2 and then back to 0,0,0 but continue adding +1 so it is 3,3,3,4,4,4 etc.
| JSON_Name | ConnectionID |
| 0 | A123 |
| 0 | A123 |
| 0 | A123 |
| 1 | A123 |
| 1 | A123 |
| 1 | A123 |
| 2 | A123 |
| 2 | A123 |
| 2 | A123 |
| 0 | B123 |
| 0 | B123 |
| 0 | B123 |
| 1 | B123 |
| 1 | B123 |
| 1 | B123 |
Please let me know, if my question doesn't make sense 
Thank in advance!
Hello experts!
I'm currently in the process of building API endpoints through Alteryx. I have managed to do that where I'm basically using the Download Tool and JSON Tool. After this, I'm filtering the JSON Name by CrossTab (each record has a number 0,0,0,1,1,1,2,2,2, so I'm basically grouping them based on the duplicate integers)
However, here is the catch: When I add a second endpoint, the JSON Name goes from 0,0,0,1,1,1,2,2,2 and then back to 0,0,0,1,1,1 which is fine (it is behaving as it should), but my issue is that when I want to use the CrossTab it only takes the unique records, so the second endpoint is not being transformed by the CrossTab.
Ideally what I would like is that it compares if that number already exists, if it does then just continue from the last highest record, so in this example it should not go from 2,2,2 and then back to 0,0,0 but continue adding +1 so it is 3,3,3,4,4,4 etc.
| JSON_Name | ConnectionID |
| 0 | A123 |
| 0 | A123 |
| 0 | A123 |
| 1 | A123 |
| 1 | A123 |
| 1 | A123 |
| 2 | A123 |
| 2 | A123 |
| 2 | A123 |
| 0 | B123 |
| 0 | B123 |
| 0 | B123 |
| 1 | B123 |
| 1 | B123 |
| 1 | B123 |
Please let me know, if my question doesn't make sense
Thank in advance!
That was exactly what I was looking for! Thank you 
Good to know about the Tile tool!
