We are running DOMO on top of Snowflake DB. My problem relates to a detailed view of a card, something like this:
DOMO data view
https://imagizer.imageshack.com/img923/1998/8P7Azo.jpg
To get this results displayed, DOMO runs a DB query which looks something like this:
SELECT <columns>
FROM <the table>
LIMIT 50 OFFSET 50
If the dataset is bigger than 50 rows, you need to scroll down using the slide bar to get the another 50 rows loaded into the DOMO view:
DOMO sidebar
https://imagizer.imageshack.com/img924/9928/iRRkjJ.jpg
Now, when you do that, the DOMO engine runs exactly the same query as above to retrieve the rows.
SELECT <columns>
FROM <the table>
LIMIT 50 OFFSET 50
I think you already see my problem, anytime I use the sidebar, it loads 50 random rows from the WHOLE dataset, so eventually, the DOMO view ends up with duplicates or missing rows entirely.
I also know that the SHARE/EXCEL EXPORT button works well, as the LIMIT in that query is rather huge, but I'd like to fix the results in the DOMO view.
Is there any way or a trick how to remedy this issue?
Related
Please help me understand the process on how we can achieve this.
I want to restrict the number of records being displayed in the canvas . If there are 1000 records in the datablock, then in the canvas I will restrict it to 100 records. For viewing the remaining 900 records we will have to provide the user with a next / previous button . When they press the next button then the next 100 records should be displayed and previous button the exact reverse.
Is this doable in Oracle Forms (like it is in Oracle Apex)?
If this is doable could anyone please provide a sample link so that I can do research on it. Not finding any good leads. Any assistance is much appreciated. Thanks.
Forms doesn't work in pages (so that you could move from one page of records to another; something like Apex does). All records fetched into the tabular block are there, that's why you have a scrollbar.
Displaying 100 records is a little bit too much; you can't see it on the screen anyway. Consider lower number, e.g. 15 records at a time.
Then, you could create those NEXT and PREVIOUS buttons. Create WHEN-BUTTON-PRESSED triggers on each of them. You'd use :system.cursor_record or :system.trigger_record as they show which record you're in now, and then move 15 records up or down. Something like this:
-- NEXT button:
go_record(:system.cursor_record + 15);
--PREVIOUS button:
go_record(:system.cursor_record - 15);
Hello Haskell and Threepenny-GUI community,
I want to display a ListBox which has infinite scrolling support. I have a table in an SQLite database with 100k - 1000k rows. I want to display rows in a ListBox. I got help from this post threepenny-gui-reactive-in-client-server. I got the GUI working with two ListBoxes, one for the page number and the other for actual rows for that page.
Though my goal is to create a GUI that has just one display, something like a basic version but similar to this example using SlickGrid: http://mleibman.github.io/SlickGrid/examples/example4-model.html.
Just a quick question, everytime I hit "edit" "add row" it adds the row but not at the bottom of the table, it usually places it like 5-10 rows from the bottom and while it's not a huge deal it's just time consuming to move it and confusing at times because they're random rows all over now. Is their a setting or a certain way to add rows so they just get added to the bottom of the fusion table instead of randomly throughout?
The rows will not be displayed randomly.
They will be displayed based on the order-settings.
When you didn't define a sort-column they will be ordered by their internal rowID, and that's the issue: the rowID's are not consecutive.
So the answer is: No, you can't.
The only workaround would be to add another column with a incrementing Number(and sort by this column), but I wouldn't suggest it.
I have the problem, that my program is too slow in displaying a flexTable. I've searched how to display the table faster and I think with a cell table it might be faster. The problem now is, there are different objects displayed in the table and I don't know how to do that with a celltable. I have a list<DTOEmployeeWithTask> and each dTOEmployeeWithTask has a list<TaskRelation>. First there's displayed a row with the employee and then each taskRelation for the employee, like this:
Now to my questions: what is the fastest way to display such a table? If it's with a cellTable, how would I do that in a CellTable?
If you need some code just say what you need.
FlexTable is a no go anyway as it's known to be slow. What would be a good solution is a Custom DataGrid, which can display rows with sub rows as in your screenshot. The GWT showcase page has a nice example including source code which should help you further: http://gwt.googleusercontent.com/samples/Showcase/Showcase.html#!CwCustomDataGrid
I need to change the orientation of a table in a BIRT report so that the table header is vertical instead of horizontal.
Is this possible? I don't want to use a Crosstab.
It seems this thread is still being pointed at so I posted an example of a horizontal table layout using a crosstab. I know it won't help the original author but others following this thread now may find this helpful.
To create the horizontal grouping, first create your query like normal, then create a Data Cube. In this data cube, drag each field that you want into a group. Then drag a new crosstab on the report and drag each field into the top right column group area. It will create a new header row for each field. Don't put anything in the left side (Rows) and don't put anything in the measure field (bottom-right). This will create labels on the left... and the data will extend out to the right.
The report design example can be downloaded from: http://developer.actuate.com/community/forum/index.php?/files/file/1079-horizontal-table-using-crosstab/
Virgil
If you want dataset records to be reported across the page, this would have to be done via a crosstab.
If you want dataset records to be reported down the page, this can't be done automatically as far as I know. However, it can be done by inserting a new detail line in your report table object for each database field to be reported, then moving column headings from the heading row into the first column's detail rows and moving record values into the second column's detail rows.
So, for example, a report with 6 columns in it would become a two column report with six detail rows.
Not in box (up to 3.7). You have to use 3'd party libs like that one.