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.
Hello #AlteryxAddicts, tl;dr tl;dr - Alteryx Partners leveraging the Designer API via .NET should not upgrade to Alteryx Designer 11.8, 2018.1, or 2018.2 because doing so will render API integration inoperable. The issue will be addressed in Alteryx Designer 2018.3 (expected GA end of August 2018) at which time users can safely upgrade. FAQ What Happened? We uncovered a previously unknown issue that renders the Designer API from .NET inoperable for Alteryx Designer 11.8, 2018.1, & 2018.2 (NOTE: API code itself is sound, the issue is 100% attributable to licensing). What is the Designer API? This notice is specifically for APIs accessed via the .NET assemblies such as “Allocate.Net.dll” and “AlteryxAPI.Net.dll”, documentation found on page 1 of: [installdirectory]\Alteryx\APIs\readme.pdf. Why did this happen? In our work to improve the Alteryx Designer Licensing experience, we inadvertently broke the ability to license API in Designer when using the .NET assemblies. This issue was identified and resolved in a timely manner and is expected to be resolved in Alteryx Designer 2018.3. What will this problem look like? - The user will receive a message that the API is not licensed. Who's Impacted? - Anyone leveraging Alteryx API on Designer 11.8, 2018.1, and/or 2018.2. Who's Not Impacted? Anyone leveraging Alteryx Designer API in Alteryx 11.7 and older. Alteryx Designer APIs accessed via C++ or the CLI were not impacted and will continue to work as expected. When will the issue be fixed? Alteryx Designer 2018.3 (expected GA end of August 2018) Next Steps? If you are using 11.8, 2018.1, 2018.2 and the Alteryx API, this issue directly impact you. We recommend downgrading to 11.7 until 2018.3 is released. Otherwise, wait until 2018.3 is released and use API integration with it. NOTE: You can also use Alteryx 11.7 and older without interruption until you choose to upgrade to 2018.3 (or future releases). Questions? Contact firstname.lastname@example.org Alter Everything! -- Alteryx Product Extensibility team
Imagine this – you’re on vacation. You’re on a sandy beach where the sun has been relentless all day. It’s hot and you need something to cool you off. Ice cream would be perfect! The Find Nearest tool can help!
You’re creating an app that involves dates. You want the user to be able to dynamically select the dates being used in the app, though. The tools you already know may not work. A Text Box would be too messy and allow lots of room for error. Pre-defined Drop Downs and List Boxes aren’t dynamic enough. Ah ha! What about that tool that looks like a calendar? The Date tool in the Interface category provides the perfect solution!
Trying to convert all of your old, mundane Excel workbooks into Alteryx workflows? The Running Total Tool could be the key to your success! You know, it’s that tool in the Transform category with the little running man picture on it.
This directory was generated by the Alteryx install script, and contains an instance of the Oracle Instant Client. Oracle Instant Client is a collection of installed Oracle Database libraries for connecting Alteryx Designer to local or remote Oracle Databases. There’s no need for tnsnames.ora file.
In this post, a user asked if you can merge cells in the Table Tool like you can in excel. There are lots of ways you can get creative with the Table Tool, for example you can have your report span across the page in multiple columns as described here or you can add totals to your data to add to your report or create headers and sub-headers as described here.
So, how do you merge cells using the Table Tool itself? You can merge cells by nesting a table inside another table:
Tables can be nested more than one deep, you could start off with city, roll up to region, and then to state:
To clean up the doubled up header rows that are created when nesting tables like that, deselect "show column headings" in the Table Tools' settings:
.... and create the header row in a separate Table Tool. In this example, we are also changing the background color and making the font bigger, and changing the wording to "Region" for the Region column:
Lastly, there should also be subtotals for each region. As with anything in Alteryx, there are different ways of doing this, they could be added as described in this post, or the process used to create the headers can be used. First, the data is summed to create totals, then the totals are put into tables grouped by region:
Lastly, the table snippets are combined in a Layout Tool using the "Vertical Merge Contents to Line Up Table Columns" option:
Also see the attached v2018.1 workflow for the complete example.
What does this error mean?
As we transitioned to a new licensing system in the 11.8 and 2018.1 releases, we changed how licenses are authenticated. The new licensing system relies on a few additional system requirements, including a number of websites that are used during licensing and require access through your network firewall.
What's causing this?
The new licensing system uses a TLS connection with fno.devops.alteryx.com, which is secured with an Amazon-issued TLS/SSL certificate. Alteryx is packaged with a copy of the Amazon certificate. The problem arises when the network has implemented Deep Packet Inspection on TLS/SSL connections, which is a security measure requiring that a network device be able to intercept the connection and “see” the plaintext conversation. To do this, the device attempts to impersonate fno.devops.alteryx.com but uses its own certificate, which is separately installed as a trusted root certificate on the client computer. However, Alteryx doesn't consult the local computer's trust store when authenticating the license connection. Thus, when Alteryx attempts to construct a TLS session, it sees a certificate mismatch, and the connection fails.
Since this is a network security restriction, you should have no problem activating if you move onto an external network such as a mobile hotspot, home network connection, or coffee shop.
How to confirm the problem
To definitively confirm that they are running into this issue, have them open a browser and go to https://fno.devops.alteryx.com. It will show a blank screen, but up in the corner is certificate information. Click on the lock to view the certificate details.
This window needs to show this exact certification Path. If there are any extra or different entries, that's when this issue occurs.
How to fix it?
IT or your security department need to add a bypass on the SSL packet inspector such that https://fno.devops.alteryx.com is not subject to SSL deep packet inspection. After adding the bypass so this traffic is no longer being interdicted, the issue should be resolved and the customer should try to activate again.