You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current fieldCalculated class does not clearly differentiate between calculated fields and native Salesforce object fields. This lack of visual or structural distinction makes it difficult to identify which fields are dependent and which are part of the original Salesforce schema, leading to confusion and inefficiencies during use.
Describe the solution you'd like
Introduce enhancements to the fieldCalculated class to improve clarity:
Apply bold text or a distinct color to make calculated fields stand out visually.
Add an extra column to explicitly indicate whether a field is a formula or a lookup.
Describe alternatives you've considered
Alternatively, append a suffix, such as [F], to fields that are formulas, providing immediate recognition of their type.
Additional context
The text was updated successfully, but these errors were encountered:
lrlip
changed the title
[Show-All-Data] Make the class fieldCalculated more visible be increasing the font-weight
[show-all-data] Make the class fieldCalculated more visible be increasing the font-weight
Dec 12, 2024
lrlip
changed the title
[show-all-data] Make the class fieldCalculated more visible be increasing the font-weight
[show-all-data] Make the class fieldCalculated more visible by increasing the font-weight
Dec 12, 2024
Yes indeed. In Salesforce, a * indicates a required field, while in the extension, it marks a calculated field, and required fields are written out explicitly. Aligning these conventions provides a better user experience.
Is your feature request related to a problem? Please describe.
The current
fieldCalculated
class does not clearly differentiate between calculated fields and native Salesforce object fields. This lack of visual or structural distinction makes it difficult to identify which fields are dependent and which are part of the original Salesforce schema, leading to confusion and inefficiencies during use.Describe the solution you'd like
Introduce enhancements to the
fieldCalculated
class to improve clarity:Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: