[jira] Created: (OFBIZ-2486) Next button/link on Physical Inventory Screen does not work

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (OFBIZ-2486) Next button/link on Physical Inventory Screen does not work

Nicolas Malin (Jira)
Next button/link on Physical Inventory Screen does not work
-----------------------------------------------------------

                 Key: OFBIZ-2486
                 URL: https://issues.apache.org/jira/browse/OFBIZ-2486
             Project: OFBiz
          Issue Type: Bug
          Components: product
    Affects Versions: Release Branch 4.0
         Environment: Sql Server 2005
            Reporter: Brian Sanders


To reproduce (requires > 100 inventory items, which should already be there):
Goto Facility > WebStoreWarehouse > Physical Inventory
Input "%" as the product id
Scroll to the bottom and click Next

The problem is that the facilityId is in the query string 2 times which yields the following query on SQL Server 2005:
SELECT
PR.FACILITY_ID, II.COMMENTS, PR.PRODUCT_ID, PR.PRODUCT_TYPE_ID, PR.PRIMARY_PRODUCT_CATEGORY_ID, PR.MANUFACTURER_PARTY_ID, PR.INTRODUCTION_DATE, PR.SUPPORT_DISCONTINUATION_DATE, PR.SALES_DISCONTINUATION_DATE, PR.SALES_DISC_WHEN_NOT_AVAIL, PR.INTERNAL_NAME, PR.BRAND_NAME, PR.COMMENTS, PR.PRODUCT_NAME, PR.DESCRIPTION, PR.LONG_DESCRIPTION, PR.PRICE_DETAIL_TEXT, PR.SMALL_IMAGE_URL, PR.MEDIUM_IMAGE_URL, PR.LARGE_IMAGE_URL, PR.DETAIL_IMAGE_URL, PR.DETAIL_SCREEN, PR.INVENTORY_MESSAGE, PR.REQUIRE_INVENTORY, PR.QUANTITY_UOM_ID, PR.QUANTITY_INCLUDED, PR.PIECES_INCLUDED, PR.REQUIRE_AMOUNT, PR.FIXED_AMOUNT, PR.AMOUNT_UOM_TYPE_ID, PR.WEIGHT_UOM_ID, PR.WEIGHT, PR.HEIGHT_UOM_ID, PR.PRODUCT_HEIGHT, PR.SHIPPING_HEIGHT, PR.WIDTH_UOM_ID, PR.PRODUCT_WIDTH, PR.SHIPPING_WIDTH, PR.DEPTH_UOM_ID, PR.PRODUCT_DEPTH, PR.SHIPPING_DEPTH, PR.PRODUCT_RATING, PR.RATING_TYPE_ENUM, PR.RETURNABLE, PR.TAXABLE, PR.TAX_CATEGORY, PR.TAX_VAT_CODE, PR.TAX_DUTY_CODE, PR.CHARGE_SHIPPING, PR.AUTO_CREATE_KEYWORDS, PR.INCLUDE_IN_PROMOTIONS, PR.IS_VIRTUAL, PR.IS_VARIANT, PR.ORIGIN_GEO_ID, PR.REQUIREMENT_METHOD_ENUM_ID, PR.BILL_OF_MATERIAL_LEVEL, PR.RESERV_MAX_PERSONS, PR.RESERV2ND_P_P_PERC, PR.RESERV_NTH_P_P_PERC, PR.CREATED_DATE, PR.CREATED_BY_USER_LOGIN, PR.LAST_MODIFIED_DATE, PR.LAST_MODIFIED_BY_USER_LOGIN, PR.IN_SHIPPING_BOX, II.INVENTORY_ITEM_ID, II.INVENTORY_ITEM_TYPE_ID, II.PARTY_ID, II.OWNER_PARTY_ID, II.STATUS_ID, II.DATETIME_RECEIVED, II.DATETIME_MANUFACTURED, II.EXPIRE_DATE, II.FACILITY_ID, II.CONTAINER_ID, II.LOT_ID, II.UOM_ID, II.BIN_NUMBER, II.LOCATION_SEQ_ID, II.QUANTITY_ON_HAND_TOTAL, II.AVAILABLE_TO_PROMISE_TOTAL, II.QUANTITY_ON_HAND, II.AVAILABLE_TO_PROMISE, II.SERIAL_NUMBER, II.SOFT_IDENTIFIER, II.ACTIVATION_NUMBER, II.ACTIVATION_VALID_THRU, II.UNIT_COST, II.CURRENCY_UOM_ID
FROM dbo.PRODUCT PR
INNER JOIN dbo.INVENTORY_ITEM II ON PR.PRODUCT_ID = II.PRODUCT_ID
WHERE (II.FACILITY_ID = ( @P0, @P1 ) AND II.INVENTORY_ITEM_TYPE_ID = @P2 AND PR.PRODUCT_ID LIKE @P3)
ORDER BY PR.PRODUCT_ID ASC

II.FACILITY_ID = ( @P0, @P1 ) is not valid SQL syntax

I tested for the bug in 9.04 and it is not there. If I modify the URL by removing the redundant facilityId, it works.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (OFBIZ-2486) Next button/link on Physical Inventory Screen does not work

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Sanders updated OFBIZ-2486:
---------------------------------

    Fix Version/s: Release Branch 4.0

> Next button/link on Physical Inventory Screen does not work
> -----------------------------------------------------------
>
>                 Key: OFBIZ-2486
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2486
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: Release Branch 4.0
>         Environment: Sql Server 2005
>            Reporter: Brian Sanders
>             Fix For: Release Branch 4.0
>
>
> To reproduce (requires > 100 inventory items, which should already be there):
> Goto Facility > WebStoreWarehouse > Physical Inventory
> Input "%" as the product id
> Scroll to the bottom and click Next
> The problem is that the facilityId is in the query string 2 times which yields the following query on SQL Server 2005:
> SELECT
> PR.FACILITY_ID, II.COMMENTS, PR.PRODUCT_ID, PR.PRODUCT_TYPE_ID, PR.PRIMARY_PRODUCT_CATEGORY_ID, PR.MANUFACTURER_PARTY_ID, PR.INTRODUCTION_DATE, PR.SUPPORT_DISCONTINUATION_DATE, PR.SALES_DISCONTINUATION_DATE, PR.SALES_DISC_WHEN_NOT_AVAIL, PR.INTERNAL_NAME, PR.BRAND_NAME, PR.COMMENTS, PR.PRODUCT_NAME, PR.DESCRIPTION, PR.LONG_DESCRIPTION, PR.PRICE_DETAIL_TEXT, PR.SMALL_IMAGE_URL, PR.MEDIUM_IMAGE_URL, PR.LARGE_IMAGE_URL, PR.DETAIL_IMAGE_URL, PR.DETAIL_SCREEN, PR.INVENTORY_MESSAGE, PR.REQUIRE_INVENTORY, PR.QUANTITY_UOM_ID, PR.QUANTITY_INCLUDED, PR.PIECES_INCLUDED, PR.REQUIRE_AMOUNT, PR.FIXED_AMOUNT, PR.AMOUNT_UOM_TYPE_ID, PR.WEIGHT_UOM_ID, PR.WEIGHT, PR.HEIGHT_UOM_ID, PR.PRODUCT_HEIGHT, PR.SHIPPING_HEIGHT, PR.WIDTH_UOM_ID, PR.PRODUCT_WIDTH, PR.SHIPPING_WIDTH, PR.DEPTH_UOM_ID, PR.PRODUCT_DEPTH, PR.SHIPPING_DEPTH, PR.PRODUCT_RATING, PR.RATING_TYPE_ENUM, PR.RETURNABLE, PR.TAXABLE, PR.TAX_CATEGORY, PR.TAX_VAT_CODE, PR.TAX_DUTY_CODE, PR.CHARGE_SHIPPING, PR.AUTO_CREATE_KEYWORDS, PR.INCLUDE_IN_PROMOTIONS, PR.IS_VIRTUAL, PR.IS_VARIANT, PR.ORIGIN_GEO_ID, PR.REQUIREMENT_METHOD_ENUM_ID, PR.BILL_OF_MATERIAL_LEVEL, PR.RESERV_MAX_PERSONS, PR.RESERV2ND_P_P_PERC, PR.RESERV_NTH_P_P_PERC, PR.CREATED_DATE, PR.CREATED_BY_USER_LOGIN, PR.LAST_MODIFIED_DATE, PR.LAST_MODIFIED_BY_USER_LOGIN, PR.IN_SHIPPING_BOX, II.INVENTORY_ITEM_ID, II.INVENTORY_ITEM_TYPE_ID, II.PARTY_ID, II.OWNER_PARTY_ID, II.STATUS_ID, II.DATETIME_RECEIVED, II.DATETIME_MANUFACTURED, II.EXPIRE_DATE, II.FACILITY_ID, II.CONTAINER_ID, II.LOT_ID, II.UOM_ID, II.BIN_NUMBER, II.LOCATION_SEQ_ID, II.QUANTITY_ON_HAND_TOTAL, II.AVAILABLE_TO_PROMISE_TOTAL, II.QUANTITY_ON_HAND, II.AVAILABLE_TO_PROMISE, II.SERIAL_NUMBER, II.SOFT_IDENTIFIER, II.ACTIVATION_NUMBER, II.ACTIVATION_VALID_THRU, II.UNIT_COST, II.CURRENCY_UOM_ID
> FROM dbo.PRODUCT PR
> INNER JOIN dbo.INVENTORY_ITEM II ON PR.PRODUCT_ID = II.PRODUCT_ID
> WHERE (II.FACILITY_ID = ( @P0, @P1 ) AND II.INVENTORY_ITEM_TYPE_ID = @P2 AND PR.PRODUCT_ID LIKE @P3)
> ORDER BY PR.PRODUCT_ID ASC
> II.FACILITY_ID = ( @P0, @P1 ) is not valid SQL syntax
> I tested for the bug in 9.04 and it is not there. If I modify the URL by removing the redundant facilityId, it works.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (OFBIZ-2486) Next button/link on Physical Inventory Screen does not work

Nicolas Malin (Jira)
In reply to this post by Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751912#action_12751912 ]

Jacques Le Roux commented on OFBIZ-2486:
----------------------------------------

Hi Brian,

Could you please provide a patch ?

Thanks

> Next button/link on Physical Inventory Screen does not work
> -----------------------------------------------------------
>
>                 Key: OFBIZ-2486
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2486
>             Project: OFBiz
>          Issue Type: Bug
>          Components: product
>    Affects Versions: Release Branch 4.0
>         Environment: Sql Server 2005
>            Reporter: Brian Sanders
>             Fix For: Release Branch 4.0
>
>
> To reproduce (requires > 100 inventory items, which should already be there):
> Goto Facility > WebStoreWarehouse > Physical Inventory
> Input "%" as the product id
> Scroll to the bottom and click Next
> The problem is that the facilityId is in the query string 2 times which yields the following query on SQL Server 2005:
> SELECT
> PR.FACILITY_ID, II.COMMENTS, PR.PRODUCT_ID, PR.PRODUCT_TYPE_ID, PR.PRIMARY_PRODUCT_CATEGORY_ID, PR.MANUFACTURER_PARTY_ID, PR.INTRODUCTION_DATE, PR.SUPPORT_DISCONTINUATION_DATE, PR.SALES_DISCONTINUATION_DATE, PR.SALES_DISC_WHEN_NOT_AVAIL, PR.INTERNAL_NAME, PR.BRAND_NAME, PR.COMMENTS, PR.PRODUCT_NAME, PR.DESCRIPTION, PR.LONG_DESCRIPTION, PR.PRICE_DETAIL_TEXT, PR.SMALL_IMAGE_URL, PR.MEDIUM_IMAGE_URL, PR.LARGE_IMAGE_URL, PR.DETAIL_IMAGE_URL, PR.DETAIL_SCREEN, PR.INVENTORY_MESSAGE, PR.REQUIRE_INVENTORY, PR.QUANTITY_UOM_ID, PR.QUANTITY_INCLUDED, PR.PIECES_INCLUDED, PR.REQUIRE_AMOUNT, PR.FIXED_AMOUNT, PR.AMOUNT_UOM_TYPE_ID, PR.WEIGHT_UOM_ID, PR.WEIGHT, PR.HEIGHT_UOM_ID, PR.PRODUCT_HEIGHT, PR.SHIPPING_HEIGHT, PR.WIDTH_UOM_ID, PR.PRODUCT_WIDTH, PR.SHIPPING_WIDTH, PR.DEPTH_UOM_ID, PR.PRODUCT_DEPTH, PR.SHIPPING_DEPTH, PR.PRODUCT_RATING, PR.RATING_TYPE_ENUM, PR.RETURNABLE, PR.TAXABLE, PR.TAX_CATEGORY, PR.TAX_VAT_CODE, PR.TAX_DUTY_CODE, PR.CHARGE_SHIPPING, PR.AUTO_CREATE_KEYWORDS, PR.INCLUDE_IN_PROMOTIONS, PR.IS_VIRTUAL, PR.IS_VARIANT, PR.ORIGIN_GEO_ID, PR.REQUIREMENT_METHOD_ENUM_ID, PR.BILL_OF_MATERIAL_LEVEL, PR.RESERV_MAX_PERSONS, PR.RESERV2ND_P_P_PERC, PR.RESERV_NTH_P_P_PERC, PR.CREATED_DATE, PR.CREATED_BY_USER_LOGIN, PR.LAST_MODIFIED_DATE, PR.LAST_MODIFIED_BY_USER_LOGIN, PR.IN_SHIPPING_BOX, II.INVENTORY_ITEM_ID, II.INVENTORY_ITEM_TYPE_ID, II.PARTY_ID, II.OWNER_PARTY_ID, II.STATUS_ID, II.DATETIME_RECEIVED, II.DATETIME_MANUFACTURED, II.EXPIRE_DATE, II.FACILITY_ID, II.CONTAINER_ID, II.LOT_ID, II.UOM_ID, II.BIN_NUMBER, II.LOCATION_SEQ_ID, II.QUANTITY_ON_HAND_TOTAL, II.AVAILABLE_TO_PROMISE_TOTAL, II.QUANTITY_ON_HAND, II.AVAILABLE_TO_PROMISE, II.SERIAL_NUMBER, II.SOFT_IDENTIFIER, II.ACTIVATION_NUMBER, II.ACTIVATION_VALID_THRU, II.UNIT_COST, II.CURRENCY_UOM_ID
> FROM dbo.PRODUCT PR
> INNER JOIN dbo.INVENTORY_ITEM II ON PR.PRODUCT_ID = II.PRODUCT_ID
> WHERE (II.FACILITY_ID = ( @P0, @P1 ) AND II.INVENTORY_ITEM_TYPE_ID = @P2 AND PR.PRODUCT_ID LIKE @P3)
> ORDER BY PR.PRODUCT_ID ASC
> II.FACILITY_ID = ( @P0, @P1 ) is not valid SQL syntax
> I tested for the bug in 9.04 and it is not there. If I modify the URL by removing the redundant facilityId, it works.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.