Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #20822 All Revisions ] Back to Issue ]
Summary 0020822: Dataset applying process leads to an error situation.
Revision 2012-06-21 09:57 by marvintm
Steps To Reproduce - Take a system/client access level entity dataset as regions and import it into client A. Information is inserted in ad_ref_data_loaded with generic_id = specific_id for regions.
- Take this dataset and now apply it to system level. Information is inserted in ad_ref_data_loaded with generic_id and specific_id=new_uuid.
- Now apply a client access level entity dataset which entity depends on the previous system/client access level entity for client A. For example taxes, that depend on regions. It works fine because there are regions for this client with generic_ids.
- After that, log in with client B and try to apply this second dependant dataset. This should work as the regions dataset has been applied to system level. It does not due to the dataset applying procedure.
   - This procedure will try to look into ad_ref_dataloaded but in his client and it will not find them.
   - Then, it will look for the generic_id into system access level data it will not find them and it will not try to look into ad_ref_data_loaded with system access level where it would find them.
- As it hasn't been able to find the regions which are referenced by the taxes, the process will fail.
Revision 2012-06-21 09:51 by marvintm
Steps To Reproduce - Take a system/client access level entity dataset as regions and import it into client A. Information is inserted in ad_ref_data_loaded with generic_id = specific_id for regions.
- Take this dataset and now apply it to system level. Information is inserted in ad_ref_data_loaded with generic_id and specific_id=new_uuid.
- Now apply a client access level entity dataset which entity depends on the previous system/client access level entity for client A. For example taxes, that depend on regions. It works fine because there are regions for this client with generic_ids.
- After that, log in with client B and try to apply this second dependant dataset. This should work as the regions dataset has been applied to system level. It does not due to the dataset applying procedure.
   - This procedure will now look into this client for generic_id regions and it will not find them.
   - Secondly, it will try to look into ad_ref_dataloaded but in his client and it will not find them.
   - Then, it will look for the generic_id into system access level data it will not find them and it will not try to look into ad_ref_data_loaded with system access level where it would find them.
- Therefore, the dataset will not be applied while it should.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker