Adrian Williams
- Total activity 243
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 89
Activity overview
Latest activity by Adrian Williams-
Adrian Williams commented,
You can use the Data3Sixty Analyze API to obtain a list of the execution states of scheduled runs. See the API documentation for your system in the integrated Help (see the 'System administration' ...
-
Adrian Williams created an article,
Lavastorm Analytic Engine End of Support Date Extension
Effective: August 8, 2019 To demonstrate Infogix’s commitment to customers who have made a significant investment in the former Lavastorm products, we are pleased to extend the support of the gen...
-
Adrian Williams commented,
This was handled as a support ticket.
-
Adrian Williams commented,
This is being handled directly as a support ticket.
-
Adrian Williams commented,
Hi Saranee, In general it is better to not have a node fail in the first instance but rather construct the logic so that the upstream node from the MetaCheck node outputs zero records when the rele...
-
Adrian Williams commented,
A support ticket has been raised to enables us to discuss this in more detail.
-
Adrian Williams commented,
You should be able to use the <Close> button to return to the canvas. It looks like there are still some instances of the library nodes on the canvas. You should then be able to delete them.
-
Adrian Williams created an article,
Data3Sixty® Analyze 3.4.3 is Now Available - LTS Release
ATTENTION: In order to continue receiving product update notices, please Sign In and select “Follow” on the Data3Sixty Analyze announcements page here. Infogix are pleased to announce the D...
-
Adrian Williams created an article,
v3.4.3 - August 2019
Data3Sixty® Analyze enhancements in this Long Term Support release include: Node Enhancements JDBC Nodes The JDBC Execute, JDBC Query and JDBC Store nodes now allow you to specify key=value pairs o...
-
Adrian Williams commented,
Per the response to your corresponding support ticket, we believe the issue was actually caused by the presence of the Euro symbol € in the name of another field in the data set.