Supply chain | Supply Chain Management, Commerce

Inquiry form using query

(1) Share

Report

Posted on by faiz7049

1,883

Hi Experts,

I have created inquiry Form to review the Rate From City and To Destination using AOT query . In Form, ZipCode is there.

I have created query as below:

But ZipCode in table LogisticAddressZipCode have somehow created three State for ZipCode 1 and we can not able to delete record since it has transaction.

My Inquiry Form is show all ZipCode=1 as below:

I want to created checkbox on LogisticsAddressSetup next to Zip/Postal Code. And only checked value should show in my inquiry Form.

Please guide me how to do it.

Thanks,

Faiz

All responses (2)

Answers (0)

faiz7049 1,883 on at

Like (0)

Report

Inquiry form using query

Hi Jonas,

Thanks for reply.

Please see below screenshot for Rating metadata

I have removed table LogisticsAddressZipCode from my query because due to relation it is duplicating records as I described previously. You can see my Inquiry from below without From City and To City name.

Please what is the best way to add From City and To City Name.

Thanks,

Faiz
Suggested answer

Jonas "Jones" Melgaard 1,983 on at

Like (0)

Report

Inquiry form using query

Hi Faiz,

To answer your question, it’s a matter of adding a NoYes field to the LogisticsAddressZipCode table and including it in the related forms. You could call it something like "Exclude from rating details."

Also, please include country in your relation. ZIP codes are not unique. It's difficult since that table needs to support all the different ZIP code formats in the world.

However, you should consider modifying your query instead. I'd add additional dimensions from the route master (for example add state) and apply a range to filter out the zip codes with a city.

Ideally, if you have the time to do so, you should create a view that groups the fields you need to display instead of using the LogisticsAddressZipCode table directly, and then join that view.

That said, I’d like to understand how your routing metadata is configured. Are we certain that dimension 4 will always represent the ZIP code? Here’s an example from my demonstration environment: