This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
This note is to alert users of Alteryx 8.6 to 10.1 of a potential message window that may appear after updating the US and Canadian CASS engine. Subsequent to completing the CASS installation and closing the installer, some clients have reported receiving a message window stating that the program may not have been installed correctly. This message can be disregarded and will not impact dataset functionality.
The source of the problem is being identified and a fix will be included in future Alteryx software releases.
Action Simply choose ‘Cancel’ to close the Program Compatibility Assistant window. Alteryx can then be opened and workflows can be run as normal.
Was the installation of CASS successful? Yes, CASS was installed fully and all scripts have finished running.
Will this message impact my installation or existing workflows? This message is entirely cosmetic; there are no impacts to the installation or workflows.
In a situation with a large database of thousands of records, some addresses may not be valid. Inevitably, CASS will output the bad addresses along with the good addresses. The issue is that certain addresses double up on the suite. Since, in this example, the input file had address and suite in the same line the file looked similar to this: The CASS output would actually find the suite, but not add it to the CASS_Suite output. This normally would not be an issue, but it actually would add it to the CASS_AddressPlusSuite field, creating a file that in fact looked like the following: This issue is inherent to the MelissaData engine which drives the CASS tool. The best way to address the issue is to include the CASS_Results field in the output from the CASS Tool. This will give a code that notifies the user of the CASS match level. Good addresses will have a match level of AS01 or AS02, whereas bad addresses will have different codes. The entire listing of all possible CASS_Results codes is available in the Help File by searching for CASS Results. Eliminating the codes that highlight bad addresses will alleviate this issue.
In June of 2012, the USPS made a change to how a P.O. Box operates. That change now allows for a street address to be used in lieu of a P.O. Box. This format, known as a P.O. Box Street Address (PBSA), is actually the address of the post office of where the P.O. Box is located. How does this affect Alteryx? One client brought to our attention that this could potentially affect address and demographic analysis. Let's say a user has a small list of competitors and they want to run a competitive analysis. The only issue is that several of these records are using a PBSA. The demographics for these records will revolve around the post office, not the actual business. How do we combat this? The first thing to keep in mind is that Alteryx is perfect for this sort of scenario. The USPS has posted a list of their post office locations as a .txt file. Attached to this post you will find an Alteryx Zip Package that informs you of where you can find the file (hint: here) and parses it. Once it is parsed, one option would be to merge that with the D&B Business Matching Macro to validate or invalidate your list of businesses. Another option would be to take your business list and compare it to this file to find out if any businesses are using a PBSA. Either way, we have options! One final note is that it is important to remember that these are valid street addresses. While the Alteryx Street Geocoder will mark a P.O. Box as invalid, it will see these and most likely geocode them all the way to the street level. If you would like to read more about this USPS feature, click here. Until next time! Chad Follow me on Twitter! @AlteryxChad
Also, HUGE THANKS to John H. for his help with this post!