Get Inspire insights from former attendees in our AMA discussion thread on Inspire Buzz. ACEs and other community members are on call all week to answer!
community Alteryx IO Alteryx.com
alteryx Community
Search
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Close
Free Trial

Location Data Knowledge Base

Data methodologies, and Release schedules.

Uninstalled datasets cause a problem in saved workflows

LonnieY
Alteryx Alumni (Retired)
Created

on ‎11-01-2017 08:40 AM - edited on ‎08-03-2021 11:31 AM by Alteryx

Question

I have a user trying to open a workflow that used the ‘TomTom_Europe_Q4_2016’ drivetime data in the Trade Area tool. They recently replaced that with the Q1 2017 data. I checked the Change Log, but didn’t see anything specifying what the changes were for this dataset. The dataset name in the error isn’t one I had installed.

Guzzler dataset error.png

Which drivetime dataset would be the most equivalent, and are there any resources I can give the user that has specifics on the differences?

Answer

Change the workflow to use the “Most Recent Vintage” instead of a specific quarter.

Here is what appears to be happening. When a specific Guzzler version is saved in a workflow (instead of most recent vintage) and that version is uninstalled during an update, Designer can’t locate that vintage and defaults to theDbSet name specified in the installation files. The DbSet name can be cryptic and appears differently from the logical name of the dataset.

Guzzler is not the only dataset where this can happen. Any of the datasets using a specific quarter (like Calgary, Allocate or Mapping) can display the same behavior. As a best practice, use Most Recent Vintage to avoid conflicts of uninstalled datasets.

Labels: