You urgently need to change a value in BC, but the application is preventing you from doing so?
An update, import or incorrect entry may result in a value being saved that causes an error at this or another point. If this brings your production to a standstill or prevents you from working, you need a quick, pragmatic solution if your application does not offer you one. In this case, you cannot wait for someone to write a solution for you.Would you like changes at field level to be logged?
You may have the option of directly accessing the database underlying your application in order to simply change a field in an emergency, but is this change then logged? WithWould you like to view specific records at table level?
If you have the appropriate rights, you can access table contents in BC in read-only mode. However, you cannot filter this view in advance, which can take a long time when opening very large tables. You can only apply filters afterwards. With
In
In
Currently, changes (renaming) to a primary key can only be made if this key consists of exactly one attribute.
In general, calculated fields of type ‘FlowField’ and ‘FlowFilter’ cannot be changed. Neither can fields that have been marked as ‘Removed’. The values must match the data type, i.e., you cannot write text to an integer or store more characters in a text field than the specified length.
Currently, the following data types can be modified:
Changes for the following data types are still in the planning stage:
All