That certainly can be done, but I don't see a reason for doing so. If you want the record to drop out of the portal but still have the data available, just change a value in a field so that the record no longer meets a portal filter's criteria or that is a match field in the relationship. Then the record is still in the table and can be retrieved, but no longer appears in your portal.
Im not sure if that will work for my intention of saving all tagged "paid" portal row and save it on a different field notes or another portal row for all the paid portal row. Reason for such is that I want the user to be able to review all the saved and deleted paid portal row if need. But can you elaborate more on how to go about changing a value to a field and not meeting the portal filter criteria
as always.. Thanks!
The need to review and possibly even to reverse (to correct an error) such entries is precisely why I suggest that you keep the data in the same table, but change the value in a field in order to change its "status".
Let's say that you have this relationship:
Invoices::__pkInvoiceID = LineItems::_fkInvoiceID
where you place a portal to LineItems on your invoices layout to create and list all unpaid line items. Then define a number field, paid in line items and give the portal this portal filter expression: Not LineItems::Paid.
Now the portal will only display lineitems with a matching invoice id where Paid is empty or zero.
Put a button in the portal row to perform this script:
Set Field [LineItems::Paid ; True ]
And clicking the button will cause the item to disappear from the portal, but the record is still in line items so that there is any number of ways you can bring it up for review or even to return it to unpaid status. One method would be a second portal where the portal filter is reversed: LineItems::Paid.
This worked fine for us. It took a while for me to understand what to do as Iam a new filemaker pro user.
As always. Thanks a lot!