How to do a code review in alteryx
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
HI All,
I am managing one big alteryx project and now there are four people are working on same workflow.
But for us it is difficult to manage the changes/enhancements because of we all are working on same workflow.
Is there any way or tool which help us to mange the code/review the code. If something goes wrong then rollback the code for particular developer who make wrong changes instead of rollback all changes who developed by all four developers in quicker way.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I dont have expericene to develop the alteryx workflow by a team.
But just to imagin, maybe
1. divide the workflow by blocks, which each will have Person-in-charge.
2. Define clearly the data stream in and out of blocks for schema
3. A designated person oversee the whole and coordinate between blocks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @alt_tush
Very good response from @Qiu. This is essentially the way you would divide a traditional coding project. One person gets the input processes, another the transformations, etc, with a final person integrating the changes.
If you can break your workflow into blocks with clearly defined input and output contracts, you can then convert each block into a standard macro. Each developer is assigned a macro to work on. This isolates the changes at the macro level, so you can then roll-back just the macro, by replacing it with a previous version, without affecting the other parts of the workflow
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
@danilang
Thank you for the postive comment. 😁
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
The path answered by @Qiu is probably the one to follow.
If this workflow is handled by that many people, will probably result in a big one.
I would suggest to abuse of the use of standard Macros. This will result in a smaller (visually) workflow, and you will be able to delegate each macro(s) as an individual workflow to each one of the team.
Good luck on that.
Regards
Tanai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @alt_tush - I agree with the above approach. This is how we would organise development. You may also be interested in learning about version control in Alteryx. Here is an article for you: https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Alteryx-vs-Version-Control-Code-Repo-G...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I guess you already know it, but you can also easily use this workflow comparison functionality. It is graphical but aslo generate a list of the differences:
Article here:
https://community.alteryx.com/t5/Engine-Works/How-to-Compare-Two-Workflows/ba-p/840936
Sales Engineer
Alteryx

