New WeWeb Fields are not registering in DB

[tg2148 (Tom)]

New to WebWeb and its been interesting for sure.

1 - Rookie mistake - only made my XANO Metadata API key with a 30 day expiration as opposed to forever.

2 - Had to create another - but somehow my collections all disappeared.

3 - I have a form that has two fields in it. Those two fields populate the DB just fine.

4 - When I try to add fields to the WeWeb form - none of the new information gets passed to the DB - but the two OLDER fields info still does.

5 - I think this has something to do with the missing collections - but:
a) am not entirely sure and
b) don’t know how to recreate

6 - When I went back to look at notes and AI chats - I could not find how the first tow (still successful) fields were created. But they (the originals) do show up in my “addVessel” workflow as local.data.form.fields.boat_name.value and local.data.form.fields.loa_ft.value

7 - I am not sure where or how to add others.
Any help is appreciated. Thank you!

[Joyce]

Hey @tg2148

@tg2148

4 - When I try to add fields to the WeWeb form - none of the new information gets passed to the DB - but the two OLDER fields info still does.

For each field in your WeWeb form, do you have a column in Xano? For example, email, name, phone number, job_title

Also, in your Xano endpoint, do you have an input for each of the 4 fields/columns that you want to be able to update?

[tg2148 (Tom)]

Ignore my deleted posts… they represent going forwards, and then backwards, and then forwards in my progress.

So I lost my mapped items when I refreshed to try to get year_built to appear.

I kept working at it and ChatGPT and I walked through the solution show here. ChatGPT said this HTTP method would stop me from having to remap constantly.

The problem is the formula window is a bit of a mess and I still have 50 more fields to enter.

Is there a smarter and more efficient way to approach this section considering I have dozens more fields to account for?