Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.filemaker > #3171

Re: Value Not Displayed in Portal

Show all headers | View raw

On 2018-07-15 23:31:08 +0000, Charles H. Sampson said:

> Helpful Harry <HelpfulHarry@BusyWorking.com> wrote:
> 
>> On 2018-07-14 22:07:21 +0000, Charles H. Sampson said:
>>> 
>>> I have a layout containing a portal with two rows. By the nature of the
>>> database, the table for the layout has at most two related records.
>>> 
>>> For one field of the related table, only one value is shown, the value
>>> in the first row. Other fields display properly, a value in each row.
>>> 
>>> Any ideas? Anything I should check that I either left out or didn't
>>> think to do?
>> 
>> Assuming the values are meant to be different, then the two most likely
>> explanations are either that the Field is not within the first row's
>> borders in Layout mode, or that the Field is not using the same
>> relationship as the Portal.
>> 
>> Helpful Harry   :o)
> 
> I'm not quite sure what you mean by "the values are meant to be
> different", Harry. Certainly, the values are coming from two different
> records in the related table, which can be verified by the fact that
> other fields in the portal are showing distinguishing values. The values
> from the two related records are the same, but that's true for values
> from another field and they display properly.

I don't know what the data is, but it is possible that some related 
records may have the same value in the same field (for example, the 
Field might store a person's title, so you'll have multiple related 
values of "Mr" or "Mrs"). I'm assuming that for your database the 
values are actually meant to be different.



> I'm also confused by "the field is not within the first row's borders in
> layout mode". My problem is that I don't know what you mean by "the
> first row's borders". In any case, here's what the Inspector tells me:
> The top of the portal is at 2.292" and the right side is at 7.514". (The
> misfiring field is at the right of the portal.) All of the fields in the
> portal have a top of 2.292". That right-most field has a right side at
> 7.5".

In Layout Mode the portal rows have borders / edges. The related fields 
*must* be fully within the bordered area of the frst row ... if they 
are even one pixel too far and overlap the row's edges, then they can 
display "strange" data in Browse or Preview Mode.

You can only put fields in the Portal's first row in Layout Mode. When 
in Browse or Privew Modes, FileMaker replicates that row for each 
existing related record. Any fields elsewhere in the Portal in Layout 
Mode will either be ignored or display 'strange' data.

Usually the 'strange' data is a duplication because FileMaker is 
retrieve only the first Related Record's data, rather than the Portal 
Row's individual related data.



> As to your third point, the portal is showing records from the related
> table. The field is showing values from a field in that related table.

When you place a Portal on the Layout you have to choose which 
relationship it uses (aka the "Related Table" or "Table Occurrence" in 
the new terminology). When you then put the Field's into the Portal, 
you have to make sure they are coming from the same relationship in the 
pop-up menu at the top of the 'choose a field' window.

If you set the Field using a different relationship (even if it's 
actually the same data table), then it confuses FileMaker and display 
"strange" data.

The easiest way to check is in Layout Mode - look at the bootom of the 
Portal and it tells you the relationship name, then double-click the 
'strange' Field and check that the pop-up menu at the top of the 
'choose a field' window is exactly the same (you may also need to check 
in the Define Relationships window that you haven't got two 
relationships with the same name - FileMaker won't care, but it does 
make it easy for you to pick the wrong one).



> Here's a new bit of info. I've been tinkering around with some of these
> dimensions, making the portal larger, the field smaller, etc. When I do,
> the borders of the field in the first row are clearly visible, with
> white space around them. However, in the second row, this area is
> completely blank. In other words, not only is the value of the field
> missing, the entire field seems to be missing.

Sounds like it *might* be a combination of the two issues. First the 
field wasn't within the Portal's first row. When you made the row 
bigger it was then inside, but is using a different Relationship to the 
Portal.

Probably the easiest thing to do is delete that Field from the Layout. 
Then duplicate an existing Portal Field that is working properly and 
double-click the new duplicate to change which related field data it 
displays.


Helpful Harry   :o)

Back to comp.databases.filemaker | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Value Not Displayed in Portal csampson@inetworld.net (Charles H. Sampson) - 2018-07-14 15:07 -0700
  Re: Value Not Displayed in Portal Helpful Harry <HelpfulHarry@BusyWorking.com> - 2018-07-15 10:53 +1200
    Re: Value Not Displayed in Portal csampson@inetworld.net (Charles H. Sampson) - 2018-07-15 16:31 -0700
      Re: Value Not Displayed in Portal Helpful Harry <HelpfulHarry@BusyWorking.com> - 2018-07-16 14:36 +1200
  Re: Value Not Displayed in Portal Helpful Harry <HelpfulHarry@BusyWorking.com> - 2018-07-16 18:11 +1200
    Re: Value Not Displayed in Portal Howard Schlossberg <howard@nospam.fmprosolutions.com> - 2018-07-15 23:34 -0700
  Re: Value Not Displayed in Portal csampson@inetworld.net (Charles H. Sampson) - 2018-08-17 12:40 -0700
    Re: Value Not Displayed in Portal Helpful Harry <HelpfulHarry@BusyWorking.com> - 2018-08-18 11:04 +1200

csiph-web