Set Field [Task::cLogDate; Get ( CurrentDate )]
In some naming conventions, cLogDate would be calc field ... attempting to write into one would cause an error, and no new related record would be created.
Sure this is not a calculation field?
Thru the relationship, the "Allow Creation of Records" is selected.
If cLogDate is not a calculation, and is in the portal, you can add the new row without the script by using the drop down calendar to insert the Current Date in that field in the next available portal row. If no empty row is visible, you can give the portal an object name and use a short script that (1) goes to the object, and (2) goes to the last row, which will bring up a new empty row.
the cLogDate is an auto enter for creation date. I have since changed the set field in script to a different field (text) and inserted "-". The outcome, however is the same.
Wondering if the relationship creation is the issue.
Relationship before the issue was Table A -< Table B -< Table "Task".
I have since created a relationship supporting a different layout which goes:
Table A -< Table B -< Table "Task"
-< Table C >- Table D
Could tables C & D be interfering?
After recreating creating separate relationship, this does not appear to be the problem. Is there a glitch within this program? Rules don't appear to be consistently followed.
Do you have added another portal(s) for the new relationships?
In that case, the script may be targeting the wrong portal. Give the original portal an object name, and prepend this
Go to Object [ creationPortalObjectName ]
to your script.
Backing out each script line item, the problem exists with the last record not available under the allow creation when selected. Is there a fix for this?
If the button is not within the portal, you should give you portal an object name (inspector Tab1, "Name") and then use the "Go To Object ("YourPortal")" script step before selecting the last Portal row. Otherwise FM does not know which last Row it should go to.
The same is true after the commit, where you definitely loose the focus on the portal. FM will not know which first portal row to select.
If you have FM PRO Advanced use the debugger and the "Pause on Error" setting and I assume you will see an "Object missing" error.
1 of 1 people found this helpful
Does your portal have a scrollbar?
If not, give it one.
Brilliant! Not sure why but the scroll bar did it!
Thx a mil!