Default setting for Relationship

Samir Jones · 2023-08-31T12:46:18+00:00

There was an error rendering this rich post.

Samir Jones

Hello,

When there's a parent missing to a child, the Default button becomes visible.

But if there are no errors, you won't see the button.

It would be ideal if the Default button would be visible at all times, or maybe have an overview window (like the Normalize window), where you could set up the default mapping.

In the attached post below, there's a workaround, but it would be less time consuming to just use the Default button.

When updating the entities, we use a combination of Smart Import, Data Readers and Entity Editor.

It will also be easier to make changes and handover responsibility to the customer.

https://community.board.com/discussion/comment/15315#Comment_15315

Find more posts tagged with

Archived

Entity

Relationship

Status: Archived

Comments

Federico Cazzalini

Dear @Samir Jones

the "default" relationship is applied only to the "missing parent" elements.

it does not change the relationships already set (that's why if you do not have "missing parent" the button is not visible).

change this behavior and let the database developer to change all the already existing relationships with a simple click on a button is too dangerous, it is better to execute a data-reader as suggested by @Alexander Kappes

best regards,

federico

Krisztina Zappert

Hi,

I agree with Samir in that this could be a very useful function to always set as default.

We might not want to always have to export and import just in case there is a missing relationship, and we don't want to overwrite existing relationships. But we also don't go into the relationships often (especially at cusomers where we only provide support) to check if all the relationships are set up correctly or not. For this, it would be good do be able to add a Default parent even when there haven't been issues yet. So, should any orphan members arrive for any reason, the default parent will become the parent of the orphan.

I don't see any risk with this, since there already exists the csv export import workaround, and since this functionality is already in the system, we just have to wait for the first orphan to arrive. It would be nice not have to wait for orphans, but deal with them before they could arrive, and not have to deal with them by export import.

This is why I think this is a great suggestion from @Samir Jones .

Mark Cosham

I agree that this is helpful. Board 12 can exhibit odd behaviour when there is a missing relationship and not having to deal with this when items are created via data readers would be useful.

Product Management Team

Thank you for sharing your idea, @Samir Jones.

We appreciate the time and effort you put into crafting your suggestion, and we understand that it can be disappointing to hear that we won't be pursuing it at this time.

We are committed to delivering the best possible experience to our customers, and we must prioritize the features and enhancements that will have the most significant impact on your daily use of our software.

While we won't be moving forward with your suggestion, we want you to know that we value your input and appreciate your contribution to our community. We encourage you to continue submitting your ideas and suggestions in the future, as we are always open to hearing new perspectives and feedback.