Constraints issue

Alan_Cooke
11 mths ago
7replies
Answered

In Proj-Buildings I select the BUILDING NAME taken from BUILDINGS. The constraint here:

a.PROJECTS.CLIENT.NAME = b.ORGANISATION.NAME

Limits the Buildings list to those for the client/organisation. What I am trying to further constrain is to only display those not previously selected. I tried this which does not work.

a.PROJECTS.CLIENT.NAME = b.ORGANISATION.NAME and not a.BUILDINGS.'BUILDING NAME'

Below is a screen shot of the selection view:

The following view is the list of selected Buildings

I click Create record and arrive at the selection (proj-buildings) wanting to see only the balance or no buildings if all have been selected.

Is this doable?

- Fred
- 11 mths ago
- Reported - view
My wee brain is having a hard time following the structure with just words. Can you post a sample DB?
- Alan_Cooke
  
  11 mths ago
  
  Reported - view
  Fred That's going to be a tricky one. How nice would it be if we could edit the Data Model but here goes.
  
  Proj-Buildings is a Many to Many table which holds Project and Buildings selections. The first part of the constraint limits Buildings to Organisation. What I need is to limit the Buildings to only those not previously selected. For example: In Project Alpha I select Buildings 1 - 3 of 4. Later Building 4 needs to be added. When I Create record to select building 4 only that building should be listed since 1 - 3 has already been selected.
  
  Help?
- Fred
- 11 mths ago
- Reported - view
said:
The first part of the constraint limits Buildings to Organisation. What I need is to limit the Buildings to only those not previously selected. For example: In Project Alpha I select Buildings 1 - 3 of 4. Later Building 4 needs to be added. When I Create record to select building 4 only that building should be listed since 1 - 3 has already been selected.

I actually wanted a sample DB not the data model, but a flow description helps.

So Project Alpha has 4 records in Proj-Buildings to start or do you add on as needed? If you don't have a dataset that has all possible buildings related to the project then you have nothing to subtract from?
- Alan_Cooke
  
  11 mths ago
  
  Reported - view
  I will look into a sample DB but there are 4 buildings of which I have selected 3. At a later date I want to add the 4th building. When I click Create record and get the list of buildings I only want to see 4 since 1 through 3 have already been selected.
  
  There is the initial constraint for the buildings of an organisation: a.PROJECTS.CLIENT.NAME = b.ORGANISATION.NAME
  Which restricts the buildings listed to only those for b. (Buildings of a Client/Organisation common to a Project)
  
  Now added to that I need to only list those not previously chosen, 1 to 3 previously leaving 4 left to choose.
- Rafael Sanchis
  
  Rafael_Sanchis
  
  11 mths ago
  
  Reported - view
  Alan Cooke
  
  Hi Alan I'm no sure if thid is what you're thinking.
  
  Each Level is a N:1 Relationship. Each Level have a constraint.
  
  https://youtu.be/s4ItulzdafI?feature=shared
- Alan_Cooke
  
  11 mths ago
  
  Reported - view
  Not exactly but I will figure it out
- Fred
- 11 mths ago
- Reported - view
said:
there are 4 buildings of which I have selected 3. At a later date I want to add the 4th building. When I click Create record and get the list of buildings I only want to see 4 since 1 through 3 have already been selected.

I don't have your DB you so I can't be sure about paths and names, but here is a guideline.

You can get to Buildings from Projects through Client. Put that in a variable.

You can get to Proj-Building from Projects. Put that in another variable.

Then you can use great example in this post. I think the complement is the one you want.

Content aside

Status Answered
11 mths agoLast active
7Replies
86Views
3 Following

Constraints issue

7 replies

Content aside

Overview