guys, even though I'm thankful for your help, but providing the fields is not an option:
- there are possibly 20+ layers to identify
- providing the fields ('hardcoding') is not ideal due to possible schema changes
- brings unnecessary overhead for maintaining possibly hundreds of layers with the field and field infos (though this could be extracted from the layer fieldInfos but again, another complexity to the code).
the '*' thing is something I'm pretty sure lots of people and developers use as:
- it provides a clean way of informing the api use the default api
- it guarantees the uniformity between popups
- there is no requirement to know anything about the fields
The only thing I can do is to create a helper function that will create a template content that will mimic the default one, but this has a major downside too:
- with each API change there is a high probability the design of the default content template will change, so I will have to update the code as well.
Again, I would advise on taking a considerate approach if you plan on 'breaking' things to something that was around since version 1.x
Thank you and with regards