Feature request #18581
More options for populating auxiliary field data
Status: | Open | ||
---|---|---|---|
Priority: | Normal | ||
Assignee: | - | ||
Category: | Attribute table | ||
Pull Request or Patch supplied: | No | Resolution: | |
Easy fix?: | No | Copied to github as #: | 26469 |
Description
Would like more options/flexibility in migrating data from my existing data-defined fields (e.g., for labeling) into the new auxiliary storage, and for modifying the auxiliary data generally.
For example, in the Attribute Table, I normally can populate fields by expression with "Update all" or "Update selected"; however, I cannot choose the auxiliary fields in the drop-down menu (even if unhidden). (I can update a data field with values from an auxiliary field, but not vice versa.) Similarly, in Field Calculator, the aux fields are not available to be updated. It would be ideal to modify aux fields in all the same ways as data fields, either within the attribute table, or a separate table for auxiliary data.
In Edit->Modify Selected Features, I can enter a value for the auxiliary fields, but the changes do not commit when I close the dialog. (The aux fields remain unpopulated.)
In Layer Properties->Auxiliary Storage, it would be helpful to designate a default value for aux fields. (This is possible in Attributes Form, but gives unpredictable results.)
In Merge Attributes of Selected Features, I can successfully enter a manual value for the aux fields, but not expressions that relate to other fields.
Related issues
History
#1 Updated by Harrissou Santanna over 6 years ago
Hi Nathan,
It's often better to split requests in smaller chunks: a request <-> a report. It'll ease discussion about each particular request and also, requests may not be of the same level/complexity/interest so can be implemented in different steps, by different devs.
This to say that some point you mention is also available in #18055 and I wonder if your report is not more of a bug report type than a feature request (easier to decide if they were separate reports).
#2 Updated by Harrissou Santanna over 6 years ago
- Related to Feature request #18055: QGIS3 - Auxiliary fields cannot be uptated through the field calculator added
#3 Updated by Nathan Perry over 6 years ago
Harrissou Santanna wrote:
Hi Nathan,
It's often better to split requests in smaller chunks: a request <-> a report. It'll ease discussion about each particular request and also, requests may not be of the same level/complexity/interest so can be implemented in different steps, by different devs.
This to say that some point you mention is also available in #18055 and I wonder if your report is not more of a bug report type than a feature request (easier to decide if they were separate reports).
Good point; I'm not certain whether some of these issues are missing features, or bugs in existing ones.
I will put in separate requests for some of the specific issues then, in case these are actual bugs.