Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

Need help using a one to one relationship for portal.


This topic is 6631 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

Ok I have a portal that works great, it shows the user the information he needs to see. However the information is tied to timestamps dates which are required for a report. So i do not want the user to change the information in the portal just view it, so I locked the fields. I have a button that sets var. from the contact table and set fields in the call table with freeze window all that, and it works.

My question is I'm trying to create another portal with one row so the user can click the new button and enter information into the 1 row and have the other portal just to see information it sort of works but the user can still change the info in the 1 row portal.

In this white paper you will see what I am having trouble with.

White paper for FM novices. Page 18.

http://www.foundationdbs.com/downloads.html

Creating a one to one relationship with a global id field as the primary key and them I'm lost.

Can anyone elaborate?

sean

  • Newbies
Posted

The tables are Contacts and Calls. The contacts table has a ContactID serial# which relates to the Calls table to ContactID with a button that performs a new record request and attaches(set field)the ContactID, the Calls table also has a unique CallID serial #. So when I am on a contact the portal shows how many calls I have made to the prospect and the result of the calls. But i want to lock the portal fields so I will not 'accidentally' change the data, because it will make my reports worthless.

So I need to find a way to create another portal???(or something else), one with one row that i can enter information and create antoher button to commit the records.

I looked at the white paper link attached above page 18, but I'm not that good at relationships.

Maybe ----create a new table one with a global ContactID---- the go Contacts::ContactID to newtable::ContactID global to Calls::ContactID then put the newtable fields on the layout and use that to enter data the click the new button to commit the records.

Thanks for your reply.

Any ideas?

This topic is 6631 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.