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

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

Recommended Posts

Posted

I have a problem with one of my relations.

It's a one-to-many relationship witch presents done items in a CRM solution. The front end field is a indexed calculation [recID|constant] and the back end is also an indexed calculation: [recID|ifItemDone].

When I created the relationship no error message occurred. It is when I'm trying to create a new related record thru a portal that I get this message: "The relationship 'logFuture' not valid and must be corrected before this field can be modified."

I've also tried to recreate the relationship and the fields it depends on, but without any change.

Am I missing something obvious here or what?

Any clues are welcome!

Thanks.

/Johan

Posted

You can't create a record via a portal if the foreign key ("back end") does not yet exist. You'll have to either use a different portal/relationship, or create the related record via a script.

Posted

Hi,

Tom is right. Make a test by reverting your relationship...

You'll see that you will be able to create related records if you had a relationship set Calc::Constant, but any relationship Constant::Calc, even if both sides are indexed will never work, and you'll get the error message.

Think of it a minute :

You're trying to create "done records" with Calc::Constant, while you can't affect the calculation "Done" from a constant.

This topic is 7856 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.