Hello Community!
I have a macro that I am going to be sharing with others - but it doesn't look very professional that when I send it over and someone puts it in their workflow, it looks like it is erroring out. Once the workflow runs, the errors don't exist - they are basically pre-checks that Alteryx is doing but they aren't actually accurate.
The two errors it is showing:
- A field doesn't exist - There is an API response that is then put through a Cross Tab tool to make the field - the field doesn't exist before the API call. In my example, it is the access_token field - once the workflow is ran, the access_token field will exist.
- A file doesn't exist - During this process, I am creating a temporary file that is stored in %Engine.TempFilePath% - that file doesn't exist until I run the workflow. Since that temporary file is used later on in the process, I get an error about the file not existing even though the workflow will be creating that file.
Again, the functionality of Alteryx is working fine. I just find these errors to be inaccurate and would like Alteryx to stop guessing if there is going to be an error before I run it - especially when the errors are dependent on if the workflow has ran or not.
Any ideas?
