How do you structure your Alteryx Projects? Designer license only

Hi Alteryx crew,

Does anyone have any ideas/links/suggestions on best practices for building folder structures for Alteryx projects? I have implemented a few different designs myself but thought it would be a great question to ask the community!

My current structure:

Projects

Project name

Alteryx

workflows go here

Archive

outdated workflows here

Data

Inbound

Outbound

Documents

Any informational documents about the project

Scripts

I write python sometimes

other automating scripts

Reporting

I'm putting tableau here for general use case but I don't actively use this at the moment

Let me know what you use and/or suggestions for what I am currently using above.

- Charles

Best Practices

Accepted answers

Hi,

Based on the design you're referencing here, There's only a few small things I would look at:

Documents

--Any informational documents about the project

Workflow

--name this whatever you'd like, concept being that anything other than a document ends up in this folder

Alteryx

--workflows go here

Archive

--outdated workflows here

Data

--Inbound

--Outbound

Scripts

--I write python sometimes

--other automating scripts

Reporting

--I'm putting tableau here for general use case but I don't actively use this at the moment

If you're using some kind of source control management software (git, tfs, etc) then the below recommendation is less applicable.

I'd also consider having a "Release" branch of some kind, so that you can do testing for changes/etc and then move stable processes into a separate location. That way even when testing you will always have an opportunity to run the "Live" version of a workflow if needed.

All comments

Hi,

Based on the design you're referencing here, There's only a few small things I would look at:

Documents

--Any informational documents about the project

Workflow

--name this whatever you'd like, concept being that anything other than a document ends up in this folder

Alteryx

--workflows go here

Archive

--outdated workflows here

Data

--Inbound

--Outbound

Scripts

--I write python sometimes

--other automating scripts

Reporting

--I'm putting tableau here for general use case but I don't actively use this at the moment

If you're using some kind of source control management software (git, tfs, etc) then the below recommendation is less applicable.

I'd also consider having a "Release" branch of some kind, so that you can do testing for changes/etc and then move stable processes into a separate location. That way even when testing you will always have an opportunity to run the "Live" version of a workflow if needed.

Awesome! Thanks for the feedback @Claje

Quick Links

Tags

This months top contributors

Hollingsworth 335