Open Forum

Expand all | Collapse all

RapidStart and tirggering validation

  • 1.  RapidStart and tirggering validation

    TOP CONTRIBUTOR
    Posted 23 days ago

    Hi All

    We have a significant add-in, one of whose features is to calculate how many racks an order takes. Imported 20,000 sales lines. All worked great, except this doesn't calculate unless I refresh the line in the UI. I'm guessing there's no way to make this happen. Do I have to write an extension to go through all lines and trigger an event?

    Thanks

    Mark



    ------------------------------
    Mark Anderson
    Director of ERP Systems
    Clesen Wholesale
    Evanston, IL
    ------------------------------
    Conference-BCNAVUG_200x200


  • 2.  RE: RapidStart and tirggering validation

    GOLD CONTRIBUTOR
    Posted 23 days ago
    %doesn't calculate unless I refresh the line in the UI

    I'm not sure I understand what that means. Is there a particular field on the line you are validating after the import?

    I will confess - I have never tried to do such a large import using rapid. I've always used custom code, but that's probably because I'm a developer (when your only tool is a hammer, all problems become nails).

    Jokes aside - I think the problem is going to be that you have no control over the order in which the table fields get validated. If you think about entering a sales line by hand, there is a certain order those fields are lined up in the subpage. Type, then No., than quantity, etc. The validation logic for those three fields prefers that order of entry. Said another way, if No. is entered first before Type, the logic doesn't know whether that is an item or a resource. With custom code, you can control the exact order of field validation. But in Rapid, that is done in the order the fields are defined in the table, not the order you might need.

    However - I think you may be able to control this. If you drill into the fields to include for the import, there is a Processing Order column that you can adjust using the Move Up and Move Down Actions. This snap is from BC15, but those fields have existing for a long time.



    ------------------------------
    Kyle Hardin
    NAV Developer
    ArcherPoint Inc.
    Duluth GA
    ------------------------------

    Conference-BCNAVUG_200x200


  • 3.  RE: RapidStart and tirggering validation

    TOP CONTRIBUTOR
    Posted 23 days ago
    Thanks for reply Kyle

    The field is from an add-in. It calculates the % of packing units for a sales line item (based on configuration templates from same add-in), so whenever I change an item, qty, or certain attributes it calculates and displays the % of a packing unit.

    I was thinking about doing a second import to see if that triggered it as all fields are already populated

    Have written a few small AL extensions, as a way of learning Al, so unless I can find a way of doing it otherwise, I may try and write an extension that triggers the necessary even on all sales lines (We need something like that for other purposes, but was planning to do it after we were live)

    Thanks

    Mark

    ------------------------------
    Mark Anderson
    Director of ERP Systems
    Clesen Wholesale
    Evanston, IL
    ------------------------------

    Conference-BCNAVUG_200x200


  • 4.  RE: RapidStart and tirggering validation

    GOLD CONTRIBUTOR
    Posted 23 days ago
    %so whenever I change an item, qty, or certain attributes it calculates and displays the % of a packing unit

    So in RAPID, set one of the certain attributes to be the last field that gets imported and validated. Move it to the bottom. That means that field (and it's validation logic) will happen after the line has everything else - all the other custom fields, quantities, units of measure, etc. I don't think you need code to solve this.

    ------------------------------
    Kyle Hardin
    NAV Developer
    ArcherPoint Inc.
    Duluth GA
    ------------------------------

    Conference-BCNAVUG_200x200


  • 5.  RE: RapidStart and tirggering validation

    TOP CONTRIBUTOR
    Posted 23 days ago
    Thanks for quick reply, Kyle

    I think I'm missing something

    I'm not importing the field that needs to be calculated, so not sure how any processing order would help

    The field in question is called CarrierQty and is calculated based on itemNo, UOM, Qty and another extension field that is looked up called container.
    I'm importing the itemNo, UOM, Qty in that processing order

    When I enter items manually, I enter, ItemNo,UOM,Qty need Container looked up, which calculates CarrierQty calculated.

    I think I'm importing fields in correct order

    ------------------------------
    Mark Anderson
    Director of ERP Systems
    Clesen Wholesale
    Evanston, IL
    ------------------------------

    Conference-BCNAVUG_200x200


If you've found this thread useful, dive deeper into User Group community content by role