What can I do with the field below the portal not updating until i click in the box?
Is it a summary field from the portal’s table?
To add to Phil's question, is it perhaps an unstored calc? And auto-enter calc? A scripted calc? And what series of steps are you going through before you feel it should update?
It could be an issue of committing the record in the portal. If you simply create a new record and enter an amount - but don't click on anything else, then that portal record hasn't been committed, and values based on that record won't update. Clicking into the 'the box' (I will assume you mean the sub-total field at the bottom of the portal) causes the related portal record to be committed and certain related calcs will be updated. (Hmmm...or does the parent record need committed, and multiple portal records could be created and edited without committing, until the parent record is committed?)
Depending on your answers to these questions will determine what you need to do. It's possible that a script trigger to commit the record would help. Or perhaps one that refreshes the layout object (you'd have to assign a name to the sub-total field in layout mode, first.)
Without knowing what you want to do, and what does the checkbox do, it‘s hard to provide help.
A bit of testing later:
* An unstored calc appears to update quite well, as each row value is edited, even if the records aren't committed.
* A summary value seems to disappear once an edit is made - until the parent record is committed (i.e. if you do things in a certain order, you can edit multiple portal records without updating the summary value, until the parent record is committed). Curiously, the summary layout object would stay invisible (it initially disappears as soon as you edit a related portal record), even after committing the record, until I hovered over it - didn't have to click or anything, just move the mouse pointer over it. (FMPA 16.03, local file, on OS X 10.11.6.)
It's quick and dirty and ugly, but I have attached my testing file. If you play around with it I suggest you add a calculation to your Data Viewer: "get(recordopenstate)". This can help you analyze when the parent record is uncommitted - but you often have to hit 'Refresh Values' for the function result to correctly reflect things.
Retrieving data ...