We have location default dimensions set up with rules of “same code”. Since BC version 22 just got installed, now we are getting ERRORS in the posting of the item reclass journals. The default dimensions from the locations come into the item reclass journal properly - the dim1 and the “new” dim1 are correct. But, we are getting dimension errors and it seems that BC is validating the location and the new location against the wrong location default dimensions. I also tried “code mandatory” in the location def dim, and setting the dimension manually, but I get the same dim ERROR. We cannot get around this - except to remove the location default dimension rule. Is anyone else experiencing this?? This is really a problem.
It sounds like there may be an issue with the default dimension rules in BC version 22 causing errors in item reclass journals. It’s possible that the validation is being done against the wrong location default dimensions. One potential workaround could be to temporarily remove the location default dimension rule and manually set the dimensions in the item reclass journal. However, this may not be a long-term solution.
It may be helpful to check with the BC support team or the community to see if others have experienced similar issues and if there is a known solution or workaround. Additionally, checking for any updates or hotfixes related to default dimensions in BC version 22 may be worth considering.
yes, I have encountered this. it is a direct result of the location now supporting default dimensions. The results can vary depending on your dimension setup and the order in which fields are validated. I suspect that Microsoft didn’t fully test the impact of this change.
I encountered this is a page used for a web service. My solution was to change the order of the fields to get the desired dimension behavior. The use of dimension priorities may also help in some situations.
Note: When a field supplies any default dimensions, it doesn’t just update the dimensions that are on the related record. Rather it recalculates all of the dimensions.
The location dimensions are defaulting correctly, and they are correct. The Dimension code and New dimension code are correct.
However, the default dimension “Value Posting” rule is being enforced incorrectly – likely because MS is not dealing with the “location code” “new location code” and “dimension code” “new dimension code” properly.
My (temporary) solution was to remove the “value posting” when they want to post item reclass journals.
This is still wrong in 22.1 (I thought I read that MS fixed this in the latest). The item reclass journal still does not understand the “reclass” part. The dimension and the new dimension are correct per the location dimension rules (from the location and the new location), but the error is not validating them correct. It seems to be validating the “dimension code” against the “new location code”.
This issue is fixed in BC Wave 2 2023 update, 23.1. Dimensions rules are respected in the Item Reclassification Journal.
1 Like