Not a 'rule', but if you create your own Save & New button you could use an API to do this.
In a formula URL field
URLRoot() & "db/" & Dbid() &
"?a=API_GenAddRecordForm" &
"&_fid_8=" & URLEncode([Field 8]) &
"&_fid_9=" & URLEncode([Field 9])
Where _fid_8 and [Field 8] are updated per your requirements (same for field 9). The URLEncode may or may not be needed depending on the type of data being passed.
For a Save & Next (not Save & New) this would be much more challenging and the 'next' record could be any record depending on where the original record was accessed and the filtering/sorting on the report. In that case, the next record's ID would be used with API_EditRecord.
However, it could be done depending on the consistency in the workflow.
If you're interested in learning more about API buttons I have a course called the
Secrets of API Buttons.
------------------------------
Quick Base Junkie
------------------------------
