I need help about DataSource on reports

Hi, sorry but i don’t speak english and i don’t know write english, but i try. I have a problem, i have a report with embedded data source, e.g. DataSource1 y Data Source 2, and I need on the report’s header show fields from my DataSource1 and on the body only show DataSource2’s fields, i have a relation 1:n between both but that doesn’t work, and if a change the DataSources relation to 1:1 that works fine, how can i list all registries from DataSource2 like a sentence FOR… or WHILE or something like that? Thank you so much. Atte.Claudia.

Try building your report using the Report Wizard (under Development Tools\Wizards) and then saving it into AOT. It really helps at the start to learn things about reports. Have you specified the Relations between the two tables under the node Relations on the embedded DS? Also try building the desing from Query. (there is an option like that in the Right-Click Menu in the design)

It’s hard to explain for me, either in english or spanish, but I’ll try. In the DataSources section of the report, you need to have the first datasource, inside of it, in his datasource you’ll need to put the other one. For example, if you need to know all the configs an itemId has. So in the report, you’ll put the InventTable as the datasource, and the ConfigTable as the DataSource of the InventTable and relate the ItemId of each table, so for each field of the InventTable, you’ll get all the ConfigTable’s fields related, the tree should look like:


Report
|-Methods
|-DataSource
    |-Query
        |-Methods
        |-Data Sources
            |-InventTable
                |-Fields
                |-Sorting
                |-Ranges
                |-Data Sources
                    |-ConfigTable
                        |-Fields
                        |-Sorting
                        |-Ranges
                        |-Data Sources
                        |-Relations
                            |-InventTable.ItemId == ConfigTable.ItemId

Hope it helps (and hope that is what you were looking for).