There are several ways to handle this.
The easiest way is to copy portal1 then rename rename poral1 to portal1b and portal2 to portal1 and paste
If that is not possible you could use a tool like MyFMbutler Clip manager, to translate the copied portal to readable text, do a search portal1 and replace with portal2
and paste it back in FileMaker.
There are also a few plugin's which can translate FM copied objects op text and back like https://www.dracoventions.com/products/2empowerFM/family/clipboard.php
Hope this helps,
Ruben van den Boogaard
Before you go and re-do the portal.
Make sure that no portal filters are on the 'damaged' portal. Or if there are then make sure the condition is evaluating as expected.
I have been in your situation before, close to pulling my hair out, to discover that a portal filter copied from another portal caused no records to appear.
Thanks, I'll have a look!
The portal was indeed a copy of a filtered one from another relationship, but creating a fresh one did not help.
The (hopefully interim) solution was to have a calculated field for the Project number in both ends. Strangely enough, it works. First I actually tried calculated entry and since that was OK, I ventured to the uncharted waters of using calculated fields in relationships. (Calculated relationships are hazardous at least in real life!)
I think there may be some confusion here. A calculation works fine in as a key field in a relationship, as long as it can be indexed. Further, even an unindexed calculation (such as, for example, an unstored calculation) can be used on the "parent" side of a relationship; it just won't work on the "child" (i.e., related) side.
Or is there some other element of calculated key fields that you're referring to as problematic? Perhaps you can post a file showing the issue.
Another thing worth checking, especially with calculated keys, is that the calculation result is set to the same data type (number, text, etc.) in both tables, otherwise the pKey and fKey may not match even if they appear to be identical.
"12345" as a text result does not match "12345" as a number result.
Correct. Thanks for the clarification, Stephen.
In the Management of External Data sources, could the file reference have changed and be incorrect? For example, did you move the other file into a folder or other location on the computer and it can't see it anymore? This type of problem is most easily avoided if the databases are both being served on a server.
In fact, Stephen, I have used calculated fields in relationships quite a few times. The situation at hand was, however, a total surprise and not an intentional construct: occurred half an hour after I had told the client that what he wanted is doable. What — me panic?