Thanks for the idea @MrRamonG when you say " the percentage a field (attribute) is populated." what specifically do you mean? The percentage of how many rows contain no data or null values, or something else?
Could you help us understand the workflow that this information would assist you with?
Hello @SSWoodward , thank you for following up. What I mean is it would be handy to know how many rows have values in an attribute, is it 100% populated, 66%, or 0% populated?
The workflow this would support would be data reviews or data audits. An attribute that is 0% populated isn't being used and may need review to see why there are no values, perhaps it is redundant, or it should just be deleted. An attribute that is partially populated, say 66%, may not be reliable for use in analysis.
The data design views focus on schema information. Including this information in the fields view would mean we would need to read the entire table every time a user opened the fields view. This would cause a significant decrease in the responsiveness of the view.
This information is best retrieved using a cursor, where you can define what constitutes 'empty' for your data set. In many cases, null is a valid attribute value and wouldn't necessarily mean that the column is not used.
