Itgensql151 on QueryTool Beta 24.1.113 on loading Fortnox inmemory table

Questions
, ,
1

Seems there is an issue with Beta 24.1.113 and Fortnox when calling a stored table @inmemorystorage inside a loop:

--
-- Case with DataDictionary : works!
--
create or replace table test@inmemorystorage
as 
select * 
from   Calendar@DataDictionary
limit  10

select * from test@inmemorystorage

declare
  my_query text;
begin
  for r in 
  ( select * 
    from test@inmemorystorage
  )
  loop
    my_query := my_query || 'my text' || r.Day_In_Week;
  end loop;
  --
  dbms_output.put_line(my_query);
end;

--
-- Case with Fortnox : raises itgensql151 error.
--
create or replace table accounts@inmemorystorage
as 
select * 
from   Accounts@fortnox
where  Active = true
;

select * 
from   accounts@inmemorystorage

declare
  my_query text;
begin
  for r in 
  ( select * 
    from accounts@inmemorystorage
  )
  loop
    my_query:= my_query || 'my text' || r.Description ;
  end loop;
  --
  dbms_output.put_line(my_query);
end;

Error:

itgensql151:
Parse error on line 6 at column 42:
Unknown field or parameter ‘R.DESCRIPTION’.
Possible valid alternative symbol names: R.Description.

Capture d’écran 2025-06-06 à 11.52.31
Capture d’écran 2025-06-06 à 11.52.311699×930 96.2 KB

This issue is not raised in Invantive Cloud, see Faster way to retrieve account balances on Fortnox

2

Strange workaround has been found.

The fields need to be named as to be found in the loop statement:

declare
  my_query text;
begin
  for r in (select Description as Description from accounts@inmemorystorage)
  loop
    my_query:= my_query || 'my text' || r.Description ;
  end loop;
  dbms_output.put_line(my_query);
end;
3

To be added: it seems the datatype resulting from the Fortnox connector are not correct, they seems like array

Capture d’écran 2025-06-06 à 17.09.44
Capture d’écran 2025-06-06 à 17.09.441384×647 60.9 KB

itgenrst004
The type of the actual data must match the data type of the column ‘ACCOUNT’ in ‘VOUCHERLINES’.
Ensure that the actual data type (çurrently ‘String’) in row #1 is cast to the data type (current ‘int32’).

4

itgensql151

The itgensql151 error can be reproduced on 24.1.114-BETA using:

declare
  l_x varchar2;
begin
  for r in (select dummy_string from DUAL@DataDictionary)
  loop
    l_x := r.dummy_string;
  end loop;
end;

It is probably caused by a major recent refactoring of column naming technology. A developer will work on a bug fix.

itgenrst004

The itgenrst004 error has already been solved in 23.1.115-BETA.

6

Any ETA on itgensql151 ?

7

There is currently no solution or ETA.

8

A fix for the naming issue described in this topic will be shipped with 24.1.122-BETA. This release is scheduled for availability early in the week of July 3, 2025.

Included in this build are also a number of other improvements due to the new naming and recognition algorithm for identifiers in SQL and PSQL.