You can delete custom fields in enterprise. Custom fields are named for example ind_1876_Feld_adressen21 or ind_2050_Feld_ObjZusatz65. Default fields from enterprise cannot be deleted.
The frontend crashes when a field is missing
If you add a (custom) field to an estate list or the detail view, and then remove that field, the frontend runs into errors.
The estate list outputs an error:
The error is this:
[onOffice-Plugin]: The API returned an error with error code 141 and the following message:
Unknown field: ind_1926_Feld_ObjZusatz39
The request that caused this error was:
{
"actionid": "urn:onoffice-de-ns:smart:2.5:smartml:action:read",
"resourceid": "",
"resourcetype": "estate",
"parameters": {
"data": [
"objekttitel",
"objektart",
"objekttyp",
"vermarktungsart",
"plz",
"ort",
"bundesland",
"objektnr_extern",
"wohnflaeche",
"grundstuecksflaeche",
"nutzflaeche",
"anzahl_zimmer",
"anzahl_badezimmer",
"kaufpreis",
"kaltmiete",
"multiParkingLot",
"ind_1926_Feld_ObjZusatz39",
"virtualAddress",
"objektadresse_freigeben",
"reserviert",
"verkauft",
"virtualStreet",
"virtualHouseNumber",
"laengengrad",
"breitengrad",
"virtualLatitude",
"virtualLongitude",
"strasse",
"showGoogleMap",
"hausnummer",
"land",
"Id"
],
"filter": {
"veroeffentlichen": [
{
"op": "=",
"val": 1
}
]
},
"estatelanguage": "ENG",
"outputlanguage": "ENG",
"listlimit": 20,
"formatoutput": true,
"addMainLangId": true,
"listoffset": 0,
"sortby": "kaltmiete",
"sortorder": "ASC"
}
}
The frontend should not crash, but it rarely happens
While we do not want the frontend to crash it this case, this issue rarely happens. So we want to set an appetite of maximum 3 days work on this.
If it takes longer, please just describe what the issues are that need to be fixed and how long roughly that would take. We will then decide whether we want to invest the work or not.
Removing a field in enterprise
You can delete custom fields in enterprise. Custom fields are named for example
ind_1876_Feld_adressen21
orind_2050_Feld_ObjZusatz65
. Default fields from enterprise cannot be deleted.The frontend crashes when a field is missing
If you add a (custom) field to an estate list or the detail view, and then remove that field, the frontend runs into errors.
The estate list outputs an error:
The error is this:
The detail page crashes:
The error is this:
Tickets regarding affected customers:
The frontend should not crash, but it rarely happens
While we do not want the frontend to crash it this case, this issue rarely happens. So we want to set an appetite of maximum 3 days work on this.
If it takes longer, please just describe what the issues are that need to be fixed and how long roughly that would take. We will then decide whether we want to invest the work or not.