To allow to rename the field names to user defined field names.
by: AFON S. | over a year ago | General Enhancements
Comments
This is required some times, good to have this
I'm assuming we're talking about field labels in the UI, as opposed to the actual table field names. If so, it would be helpful to do this without having to recompile the UI code.
That would be a support headache, just imagine telling a user to go to the XXX field and the user does not have such a field since it has been renamed. I do see the benefit though.
Yeah sometimes some standardize field would be great also, at least we are easy to support lots of customer without needing to remember the field name. But it's also good to have it. And I think this has been planned on the next 6.x release where we can change the field name.
I disagree 100%, this would be a maintenance nightmare. How do I issue a negative vote for this?
To address the ease-of-support problem, what if there were an easy way to toggle betweent the standard name and the alias name?
If you had a table where all the name changes were held eg "check" is now "cheque", "vendor" is now "supplier", "customer" is now "member" then it wouldn't be such a nightmare and if that table showed where it was changed, then support would be ok and this would be very much appreciated.
Similar to CRM functionality where you can change field names etc using Translation function. Would be helpful. Isn't this going to be a 6x feature?
I would suggest that this be set up as a 'language'. When you need to do support you flip back to 'standard' language.
In crm there is a translation feature. ERP should also have one.
Low value and high headaches. Sage should be picking sweeter fruit than this.
Simple solution for support issues - show changed field names in different colour text. I use something similar all the time in MS Access: if I change a field name for a query or a report, I simply show it in Upper/Lower case instead of UPPER which is the Access default.
Particularly useful where unused fields are used for other, specific, purposes - e.g. Comment fields in the Items table in IC being used for extended descriptions, etc.
The (UK) Sage 50 Manufacturing software allows field labels to be changed, and the changes can be 'switched off' for support purposes and then re-enabled. I think the translations/language system a la CRM would work best, however.
I agree with Rebekah H & Eva P. Allow label customization, but track it, OR as Martin M suggests, make it evident that the standard label has been changed. Sometimes unused fields ARE used for other specific purposes for good reason -- optional fields are more cumbersome to use and currently do not have as much inquiry capability as other fields on the "main" record.
would be great instead of having to modify the screen in a macro. Should be done through screen customization form.
Different languages or terminology used. Sometimes the field is for a specific parameter.
Certain industries have specific naming conventions. Allows for a more tailored experience for the user.
No dates here, so we cant tell how many years old this idea is. But its safe to say that a dog born the same day as this idea would no longer be chasing butterflies with youthful enthusiasm.
Comments
This is required some times, good to have this
I'm assuming we're talking about field labels in the UI, as opposed to the actual table field names. If so, it would be helpful to do this without having to recompile the UI code.
That would be a support headache, just imagine telling a user to go to the XXX field and the user does not have such a field since it has been renamed. I do see the benefit though.
Yeah sometimes some standardize field would be great also, at least we are easy to support lots of customer without needing to remember the field name. But it's also good to have it. And I think this has been planned on the next 6.x release where we can change the field name.
I disagree 100%, this would be a maintenance nightmare. How do I issue a negative vote for this?
To address the ease-of-support problem, what if there were an easy way to toggle betweent the standard name and the alias name?
If you had a table where all the name changes were held eg "check" is now "cheque", "vendor" is now "supplier", "customer" is now "member" then it wouldn't be such a nightmare and if that table showed where it was changed, then support would be ok and this would be very much appreciated.
Similar to CRM functionality where you can change field names etc using Translation function. Would be helpful. Isn't this going to be a 6x feature?
I would suggest that this be set up as a 'language'. When you need to do support you flip back to 'standard' language.
In crm there is a translation feature. ERP should also have one.
Low value and high headaches. Sage should be picking sweeter fruit than this.
Simple solution for support issues - show changed field names in different colour text. I use something similar all the time in MS Access: if I change a field name for a query or a report, I simply show it in Upper/Lower case instead of UPPER which is the Access default.
Particularly useful where unused fields are used for other, specific, purposes - e.g. Comment fields in the Items table in IC being used for extended descriptions, etc.
The (UK) Sage 50 Manufacturing software allows field labels to be changed, and the changes can be 'switched off' for support purposes and then re-enabled. I think the translations/language system a la CRM would work best, however.
I agree with Rebekah H & Eva P. Allow label customization, but track it, OR as Martin M suggests, make it evident that the standard label has been changed. Sometimes unused fields ARE used for other specific purposes for good reason -- optional fields are more cumbersome to use and currently do not have as much inquiry capability as other fields on the "main" record.
would be great instead of having to modify the screen in a macro. Should be done through screen customization form.
Different languages or terminology used. Sometimes the field is for a specific parameter.
Certain industries have specific naming conventions. Allows for a more tailored experience for the user.
No dates here, so we cant tell how many years old this idea is.
But its safe to say that a dog born the same day as this idea would no longer be chasing butterflies with youthful enthusiasm.
108 votes as at 12 April 2022.