1 of 1 people found this helpful
If the field truly got deleted, then the column that holds that field data in the database table (MASTERx - where x is the workspace number) would have gotten deleted., so in that case, the new field you created would not repopulate with the previously existing values.
The fact that you indicated you could recreate it (assuming you used the exact same name) tells me it was in fact deleted. But you may get an error if and when you try to publish.
But possibly the field is only hidden by role permission or something to that effect. I might advise you take this up with your support provider for detailed assistance. But, if you still see the field at "Administration | Workspace | Schema", that is an indication it does still exist and is hiding for some reason.
Thanks for replying, and so fast!
I checked the Schema and there the little bugger is. Phew! I was afraid we'd lost 13 years of room number references. So now I will open a support ticket to find out how and why the filed is hiding.
Thanks for the help!
As John said, the ultimate test for whether your data is lost is to check the database. Look for the existence of the column. Column names will differ slightly from the fields' names as they appear in the web interface: spaces will be changed to __b, hyphens will be __c, etc.
in the dev console. This should output an object which you can expand. You should see all your field names. Look for your missing field in this object. If you see any fields with strange names such as cf_0, cf_1, etc, I believe these signify fields added to the form but not yet published.
Also look at
Chrome browser is best for doing this type of troubleshooting.
RightStar Systems, Inc.
I just saw that you found your field. That's a good sign!
It probably has lost its place and doesn't live on any tab. Using the browser dev tools I mentioned a couple minutes ago, check
Expand this object and look for your field's name. Expand your field's name, and you should see a "tab" property indicating which tab the field lives on. If this property is not present, that confirms the field has gone into limbo.
Repairing this will probably involve editing that fbConfig.layout object, either through the browser's dev tools or by editing a JSON file. I expect you would need to add the "tab" property back onto the fbConfig.layout.fields.<your field name> object and also modify the fbConfig.layout.tabs object, but you should work through this with your support provider.
RightStar Systems, Inc.
Update: Well, looks like a Password change for a database account that we use for our Dynamic SQL Mappings is the cause. Why? I don't know. But I was able to recreate the room field and all the rooms showed up in the old tickets. But when troubleshooting the SQL Mappings I broke one and suddenly the room was gone again.
At least I know I can return it. Now to figure out the Dynamic SQL Mapping issue.
Thanks for your help everyone!