CMDBuild Forum

Re: Filtered Reference Attribute Lost Data on Edit/Clone

Old Versions
#1

Dear Technoteca,

I am using CMDBuild 2.1.8. Working on a large set of data often slow down data entry with reference attribute. To resolve this I have configure filter properties for the reference attributes. Consider the following scenario:

 

I have 4 classes:

Class Supplier

Class Contract

Class Equipment

Class DeliveryVoucher

 

In class DeliveryVoucher I have the following attributes:

VoucherReference (text attribute)

Supplier (reference attribute to class Supplier)

Contract (reference attribute to class Contract, I set the filter Supplier attribute)

Equipment (reference attribute to class Equipment, I set the filter to Contract attribute)

 

During the initial data entry the filter works perfectly. Keeping the choice of the next attributes to a minimum base on the previous selected attributes. But after I save the data and would like to edit or clone the card, the last attribute will always missing information. I suspect that the logical sequential firing of the filter didn't happen correctly when entering edit mode. This usually happen at the second cascaded filter. I will make a video screen capture later to show what I mean.

#2
This is the video link that show the data lost.. during clone and edit.
 
http://www.youtube.com/watch?v=J3GAueQEbro&list=UU42eo0UIfkC-FsDRCaHXcbg
 
 
 
Previously Zahri wrote:

Dear Technoteca,

I am using CMDBuild 2.1.8. Working on a large set of data often slow down data entry with reference attribute. To resolve this I have configure filter properties for the reference attributes. Consider the following scenario:

 

I have 4 classes:

Class Supplier

Class Contract

Class Equipment

Class DeliveryVoucher

 

In class DeliveryVoucher I have the following attributes:

VoucherReference (text attribute)

Supplier (reference attribute to class Supplier)

Contract (reference attribute to class Contract, I set the filter Supplier attribute)

Equipment (reference attribute to class Equipment, I set the filter to Contract attribute)

 

During the initial data entry the filter works perfectly. Keeping the choice of the next attributes to a minimum base on the previous selected attributes. But after I save the data and would like to edit or clone the card, the last attribute will always missing information. I suspect that the logical sequential firing of the filter didn't happen correctly when entering edit mode. This usually happen at the second cascaded filter. I will make a video screen capture later to show what I mean.

 

#3
Dear Technoteca,
 
Any news about this error? It has been a pain for me and my 50 users. Am I the only user facing this problem? Anybody else having the same problem as I do?
#4

Sorry for the delay.

We know that is a quite critical error but we could not put the fix in version 2.2 which will be released next week.

We have added many new features in version 2.2 and so we are already late.

The fix is planned in version 2.2.1 which will follow a few weeks later (around the end of July).

CMDBuild Team

#5
Dear Tecnoteca,
 
The acknowledgement that this is an error is what I needed to hear.. Because I have been scratching my head trying to find what I had done wrong.. Please take you time to solve it.. So, for the time being I will let my users know and we make do.. Thanks.
 
Regards,
Zahri
 
Previously Tecnoteca wrote:

Sorry for the delay.

We know that is a quite critical error but we could not put the fix in version 2.2 which will be released next week.

We have added many new features in version 2.2 and so we are already late.

The fix is planned in version 2.2.1 which will follow a few weeks later (around the end of July).

CMDBuild Team

 

#6
Dear Tecnoteca,
 
We have the same problem that has Zahri. After reading this post, we installed the version 2.2.1 but the problem recurs unchanged.
Are you confident that this version contains this bugfix? It's very important for us to have working filters.
Thanks,
Best Regards,
Samantha

 

Previously Tecnoteca wrote:

Sorry for the delay.

We know that is a quite critical error but we could not put the fix in version 2.2 which will be released next week.

We have added many new features in version 2.2 and so we are already late.

The fix is planned in version 2.2.1 which will follow a few weeks later (around the end of July).

CMDBuild Team

 

#7

We had to move forward a couple of activities because the version 2.2.1 was to come out in late July, early August maximum.
CMDBuild Team

 

 

#8
Dear Technoteca,
 
Any update on this. I am planning the update to version 2.2.1 within this month. If a fix on this issues is coming soon, I plan to wait for the fix rather than doing the update twice. Any indication on the way ahead is much appreciated. Thanks.
 
Zahri
 
Previously Tecnoteca wrote:
We had to move forward a couple of activities because the version 2.2.1 was to come out in late July, early August maximum.
CMDBuild Team

 

 

 

#9

We have worked in recent days to the solution of this bug, and now it seems to be fixed.
In the coming weeks we will do more testing and then the fix will be available in version 2.2.2, which will be released within the month of October (together with other improvements).

CMDBuild Team