Solution:
If aliases are created within a query within a data link, the alias name will need to be used within the token in the feature short / long descriptions. The token must be entered as {DataLink.fieldname}.
Example
Data Link ID: House_Information
Query: SELECT street_address AS "Address"
Feature Short / Long Description: {House_Information.Address} (as opposed to {House_Information.street_address})
The reason for this is because the field names and aliases are unknown to Essentials and the viewers at design time. They are defined in the SQL Select statement, but there aren't any parts of our software that ever interpret the SQL. This is why the Feature Description editor is unable to suggest data link fields. The fields only become known when you actually run the data link and we see the tabular result data. This data is provided by the underlying database an only includes the field aliases.
Comments
0 comments
Article is closed for comments.