Relationship + Extra Attributes

[deleted]

I understand how to relate two BO's to each other but how do you add an extra attribute to describe the relationship.

ie A company may be Electrical, Mechanical Hydraulic consultants and that is how they have been categorised in the Company business object but their relationship with a project may be only 'Electrical'. When I relate the company to the project how would I type in 'Electrical' to describe it.

TIA

aware_support

You create an additional object called RelationshipToProject and add two attributes - Type and a reference to Project. The Company object will then be related to this extra object rather than to the Project directly.

[deleted]

This seems to have done the trick.

I have found the dialog I am using has a drop down which use the project number (number) and project name (string) , fetch records dynamically (contains) when I type in a number or a string it does not find any matches.

When I remove the project number from the drop down the string search works a treat. Is there a way to force the drop down items to be a string so the search works?

Thanks

aware_support

Dynamic search in the drop down always uses strings, so if you want this to work you will need to add a Text attribute that will contain a concatenation of the number and string and then use this attribute in the drop down.

ninap

for clarification;

James/Support

can we have a drop down which was before a Zipcode like 95003-1110 which shows also the City it is related to in the dropdown?

but the actual drop down only selects the Zipcode

example;

imagine a usecase where we have 10 types of Microwaves for sale, and the drop down is the Part # - but we want the Sales persons who only know the Microwaves by Model/Type.

can we have a drop down which shows both the part # and the related model name?

txs, nina 😉

tford

You can show whatever attributes you want in the drop down of a reference record, then choose which attributes you want to show via shortcuts.

ninap

tom,

what we mean is something like this

BO: name Zipcodes has 2 attributes code (which is the actual zipcode) and city which is the Zipcodes city.

We wanted to have a drop down, which was the Zipcode.code but also shows the Zipcodes.city next to it.

This way a user can also choose the actual zipcode by City name
[/img]

[deleted]

I am trying to open the contacts detail form that is related to the project via the separate BO using the process

EDIT ProjectContact.Contact

but despite the operation button directing output to a 'New Tab' the contacts form appears in a pop up.

Any ideas on why this may be happening? Thx

BobK

Try using VIEW instead of EDIT.

[deleted]

Well, don't I feel silly. . . . Thanks

weblike

Hello,

In previous post I asked a newbie question, but I figured it out after little documentation.

Now I hope this is not stupid like the previous, but after reading, watching tutorials still can't figured it out..

I have an Order APP, with Orders and OrdersDetails BO's.

When I make them Peer Relationship the creation form it's working fine. When I create an order, in the same time I can add order_details..

If I make the Owner/child relationship between BO's ...I have to create the Order first-> save it -> only after this I am able to enter the order_details...

OK..Why I want the Owner/child relationship? Because like it's says in docs...when deleting order..all child order_details are deleted...and I don't want my DB to be messy when users begins to add/modify/delete orders...

When I open the Order form the OrderID in the form is not updated. I tried to use some rules to update the OrderID when I open the form but no luck...
I have this rule:
IF Order IS NEW THEN Order.OrderID=MAX Order.OrderID+1

I guess I have to add one more rule..but don't no what yet..
Thank you

[deleted]

gheorghe,

Not sure if you meant to post this in this thread or even if it is resolved but here are some comments.

I have a thing about deleting records in a database. I have a preference to flag them as cancelled or void and I have a hide & deleted attribute in case I want to hide them etc.

I have a process that gets the user to enter a reason for deletion and then I fake the deletion hiding it, like a trash bin. This process does all of the necessary steps checking for related records to ensure data integrity is maintained in case the administrator wants to delete it later on. Why do I do this, firstly so that an employee cannot damage the business by spitefully deleting records and also some industries need compliance where deletion is just not allowed, also as your app is an orders app the deletion of orders that have been shipped, depending on your process, should not be able to be deleted.

Regarding the order number I have a numeric attribute with auto increment selected. Your rule should work but only once the record is saved. It won't update it when the form for the new record is displayed. . . that I have noticed. If users want to add specific prefix or suffix to the order number they can via other attributes.

weblike

Thank you for your reply.

What are u saying is perfectly right. Indeed in real life this is a normal concept.
I will try to adapt my app as you said...

Indeed by mistake I posted the reply in your post...sorry for that...but u helped me a lot with your idea. Thank you...

Celtic

simialar question but as newbie need a bit more help!

Currently evaluating and have hit the wall with the reference attributes.

I have a similar business problem that relates to specifying a relationship type to an instance of a related object. Experimented with the Project and Company and Relationship to Project example but can’t seem to get it to do what I want on the data entry view.

Using the Project and Company example explained above.

Relationships
A Company can have one or more Projects
A Company will have a relationship type with each project created

User Story
When a user creates a new Company they need to be able to create one or more projects and for each project they create they need to specify the Relationship type the company has to the project.

Example
Company A has 3 projects ,but the relationship type a between each can be different,
e.g. Contractor, Client, Subcontractor type relationship

Current Configuration (could be the problem!)

-Company Object
Company.CompanyName
Company.Type (Reference to RelationshipToProject.Type, Peer, no multiple)

-RelationshipToProject Object
RelationshipToProject.Type RelationshipToProject.Project (Peer, no multiple)
RelationshipToProject.Company (reference to Company.type object, Peer, No multiple)

-Project Object
Project.ProjectName
Project.relationship (reference to RelationshipToProject.Project (Peer, Multiple)

The form design just not work out, I would want the user to be able to create a new Company, then click “add new” , on the project related form section and be able to specify the Relationship.type when creating the Project on the same row.

When I remove the RelationshipToProject you can create a company and multiple projects on one form perfectly,but of course I cannot specify the type as part of the same input.

Any ideas? Sample BSV?!!

[deleted]

Your relationship BO should have the attributes project, company and type and any others that define the record. Create the relevant relationships to the project and company table. This BO is commonly known in SQL as a join table.

Celtic

cheers James

yeah this is known as Junction object / 1:m:1 relationship thats easy to create on ms access etc and then define in a form but seems is giving me a headache!

how did you apply the mutliple / peer/parent options? just on the Project and Company objects

how did you design your form? got a screen shot?

any help appreciated! once i got this concept cracked i am on my way!

Celtic

thanks for your thoughts!

so my config is now the following

-Company Object
Company.CompanyName
Company.Type (Reference to RelationshipToProject.Type, Peer, multiple)

-RelationshipToProject Object
RelationshipToProject.Type (choice list)
RelationshipToProject.Project (reference to Project.Relationship Object, Peer, no multiple)
RelationshipToProject.Company (reference to Company.type object, Peer, No multiple)

-Project Object
Project.ProjectName
Project.relationship (reference to RelationshipToProject.Project (Peer, Multiple)

This is a pretty basic 1:M:1 relationship where RelationshipToProject is a junction object between Project and Company.

I would want the user to be able to create a new Company, then click “add new” , on the project related form section and be able to specify the Relationship.type when creating the Project on the same row.

But I cannot do this as when I try and create a form from the Project or Company side of the relationship only the Type field is available.

Can someone give me a steer on the right approach for the user interface to achieve this? Or do I need to use processes to handle this? in which case some insight on the best approach would be appreciated.

aware_support

I am not sure I understand exactly how you want to create a project related to the company. However, one idea is to use form-in-form editing for the RelationshipType object, i.e. the form of the RelationshipType object can include the form of the Project object, so that the user can specify both at once. To achieve this you need to enable inline editing of the referred object and select "Use form" radio button. Or you can use standard inline editing and enter Project details inline inside the form of the RelationshipType object.

Celtic

thanks Support

got a bit further but now jsut receive this message when trying to add a record using this method

-------------------------.
2013-04-05 11:48:46,439 ERROR TestRole#admin -Execution Exception after starting system process message Internal error. Business object EntityImpl not found in business space version

running mysql, somethign to do with that? or just that the design is the issue, if you need the bsv let me know.

aware_support

Yes, please send the BSV to support@awareim.com and describe the steps that we need to perform in this BSV to reproduce the problem