Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
I am probably missing something quite simple in my code here but can't seem to figure it out.
inputfield BudgetPrognosis;
/*************************BUDGET DATA******************************/
BudgetTemp:
CrossTable(BudgetYear, BudgetAmount, 1)
LOAD autonumber(Office & ' ' & EmployeeID) as BudgetKey,
[2005],
[2006],
[2007],
[2008],
[2009]
FROM
(biff, embedded labels, header is 1 lines, table is Sheet1$, filters(
Replace(1, top, StrCnd(null))
));
Budget:
LOAD BudgetYear,
BudgetAmount,
BudgetKey,
rowno() as Counter,
BudgetAmount as BudgetPrognosis
Resident BudgetTemp;
drop table BudgetTemp;
Resident BudgetTemp;
drop table BudgetTemp;
When I create a table box, I don't see those little interaction icons on the inputfield 'Budget Prognosis'.
However, when I do this, I am able to edit the Budget Prognosis values using the input field.
inputfield BudgetPrognosis;
/*************************BUDGET DATA******************************/
BudgetTemp:
CrossTable(BudgetYear, BudgetPrognosis, 1)
LOAD autonumber(Office & ' ' & EmployeeID) as BudgetKey,
[2005],
[2006],
[2007],
[2008],
[2009]
FROM
(biff, embedded labels, header is 1 lines, table is Sheet1$, filters(
Replace(1, top, StrCnd(null))
));
I am showing data in the table box from two tables, the above table and the SalesPerson which apparently is connected to the Budget via an Employees Table.
Keys:
(Budget {BudgetKey}
Employee {BudgetKey, EmployeeID}
SalesPerson {EmployeeID}
)
Apparently the keys are also complete.
I am using QV 10 SR3 Release 9061 (the latest)
Thanks in Advance
Tanel,
Inputfields are not compatible with Resident Loads as of QV10 SR3. A workaround would probably be to store BudgetTemp in a QVD, then load the Budget table from that QVD rather than doing a resident load. Give that a shot.
Scott
I guess inputfield does not like dropping a table BudgetTemp that contains same fields as it's final table Budget. Try to load BudgetTemp with temp fields:
inputfield BudgetPrognosis;
/*************************BUDGET DATA******************************/
BudgetTemp:
CrossTable(tmpBudgetYear, tmpBudgetAmount, 1)
LOAD autonumber(Office & ' ' & EmployeeID) as tmpBudgetKey,
[2005],
[2006],
[2007],
[2008],
[2009]
FROM
(biff, embedded labels, header is 1 lines, table is Sheet1$, filters(
Replace(1, top, StrCnd(null))
));
Budget:
LOAD tmpBudgetYear as BudgetYear,
tmpBudgetAmount as BudgetAmount,
tmpBudgetKey as BudgetKey,
rowno() as Counter,
tmpBudgetAmount as BudgetPrognosis
Resident BudgetTemp;
drop table BudgetTemp;
Hi Tanel,
Thanks for your reply. I am afraid that didn't work as well, I am still using the workaround I mentioned above but it is quite a strange behavior for me.
Would be good to have some sort of tracing on input fields to see what is really happening behind the scenes...
Regards,
Atif.
Tanel,
Inputfields are not compatible with Resident Loads as of QV10 SR3. A workaround would probably be to store BudgetTemp in a QVD, then load the Budget table from that QVD rather than doing a resident load. Give that a shot.
Scott
shanrahan wrote:
Tanel,
Inputfields are not compatible with Resident Loads as of QV10 SR3.
Oh! That is a "nice" addition. "Thanks" to QlikTech.
Your workaround works, Scott. Thanks.