I've had a bit of a think on this and can't come up with an idea for a solution.

I have a portal that will list employees. I want the user to mark a field next to one of the records in the portal to indicate they were in charge of the job. Anyone point me in the right direction so that the user is limited to having one record marked as "in charge" only?

See if this helps:

http://fmforums.com/forum/topic/78877-choosing-the-best-photo-in-nested-tables/page__p__368222#entry368222

Hi,

I'm having a difficult time trying to get the sum of the values between two dates in a portal. any idea? thanks

Not sure what you mean by that - it doesn't seem to be related to the original question in this thread.

how can i filter records in a portal, for example, between two dates?

If you are using version 10 or lower, you need to filter the relationship by adding more predicates. Usually you'd define another relationship for this using a second occurrence of the child table, for example:

Parent::ParentID = Child 2::ParentID

AND

Parent::StartDate ≤ Child 2::Date

AND

Parent::EndDate ≥ Child 2::Date

thanks!

Hi guys.

Apologies for posting here but, at present, I'm only allowed to 'reply' rather than start a new thread.

I have been pulling my hair out trying to solve the following conundrum:

What I want to do is create a 'weekly view' of appointments. At present I have no problem creating a daily view by doing the following:

• 
  
  Create APPOINTMENTS table with AppointmentDate, Time, (related) Contact ID, notes, etc
  
• 
  
  Create CALENDAR table with one field: CalendarDate
  
• 
  
  Make a CalendarDate – AppointmentDate relationship
  
• 
  
  Create a layout based on CALENDAR table
  
• 
  
  Insert CalendarDate into header
  
• 
  
  In body, create portal, containing APPOINTMENTS fields
  

In Browse mode, when I select a CalendarDate (with a drop-down calendar), the portal correctly reflects the appointments filtered by the given date. So far, so good, however...

I have tried to replicate this logic for a weekly view by doing the following:

• 
  
  Do everything listed as above for the first portal (left)
  
• 
  
  Create six more portals to the right, containing the same related fields from the APPOINTMENTS table
  
• 
  
  In the first portal to the right of the original (i.e. the second portal) I click the following: Portal Setup > Filter portal records > Specify > (Each portal record will be visible when:) > Appointments::AppointmentDate = (Calendar::CalendarDate + 1)
  
• 
  
  The third portal is filtered by Appointments::AppointmentDate = (Calendar::CalendarDate + 2), and so on.
  
• 
  

Problem is, the bugger doesn't work. Where oh where am I going wrong? I have nobody to turn to that has even the vaguest idea of how relational Dbs work so any help would quite literally make my week.

I rarely cross my fingers but this is definitely one of those times.

Cheers,

Packet.

Filtering a portal means that some related records will not be shown. If your relationship is:

Calendar::CalendarDate  = Appointments::AppointmentDate

 

and you apply a filter of:

 

Appointments::AppointmentDate = Calendar::CalendarDate + 1

then no records will be shown.