Internal Error: Invalid parameter detected in function (null). Fil
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I frequently have this error when using ODBC connection, while my query is working fine outside Alteryx. It seems to be related to the size of the results, because if I had a criteria, or modify a criteria to get a more restrictive result, it works.
What is the solution??? My query should only return 138.710 lines, from an Oracle database, which is not a big dataset at all!
Solved! Go to Solution.
- Labels:
- Bug
- Connectors
- Datasets
- Input
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
By using a direct Oracle connection, it seems to work...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Enclosing CASE WHEN statement in parenthesis solved this problem for me.
I haven't looked at your code, but often subtle formatting that works without issue outside alteryx raises issues once placed in the alteryx input tool sql editor. For example, a version of the script below only works when the case statement is enclosed.
(CASE
WHEN status IS NULL THEN segment
ELSE detail.segment
END) status,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
I got the same error with a Snowflake connection. I just used the CAST function to convert date fields into strings and that worked for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
in case it's helpful for anyone else with an Oracle DB pull, I ended up using TO_CHAR([datetimefieldname],'YYYY-MM-DD HH:MM:SS') to get around this error by converting to string.
