Since DES2 is another 'occurrence' of DES shouldn't I see the same records in DES2 that I see in DES?
What am I missing?
Not necessarily. There would need to be a valid relationship linking each record shown in your report to at least one record in DES2. Since you can add fields from that Table occurrence, you would seem to have a relationship, but it would seem that you need to check the values of the match fields used in that relationship as it would appear that at least one of those fields is either blank or has the wrong information.
In DES I originally have sample data. When I create and run the sub-summary report (based on DES2 sample data) everything works as expected.
However, after I import data from a previous version of the app into DES, the report looks as above.
I can't confirm (I don't have FM Advanced on this computer) that the Import script is not at fault but reports based on DES work.
you need to check the values of the match fields used in that relationship as it would appear that at least one of those fields is either blank or has the wrong information.
Here is the 'original' report with sample data:
After I import data from a previous version and after I run the same report, I get:
The difference seems to be caused by the import script. But if that was the case, wouldn't all DES reports misbehave?
I think the problem stems from the fact that I changed the field name of DES::Type to DES::Status. This broke the import script and subsequently the report.
So, I am puzzling a 'repair' that would look at the DES table and if it has a field called Status, then import Status-->Startus otherwise import Type-->Status.
Is there a simpler, more effective method? (Shame on me for changing the field name; but I thought FM rolled changed field names throughout the application?)