"Open With" breaks with grid customization

Epicor ERP 10
1

Hello all,

I made a customization on Part Transaction History that binds a baq to the part transaction grid (needed to display a field not available in dataset). The customization works great except for the “Open With” function on the grid. Normally, the packslip num would open with Customer Shipment Entry, but with my customization it is trying to open with “Miscellaneous Shipment Entry.” Hmmm. I really want it to open with Customer Shipment Entry, like the base form.

BASE FORM:

2
21156×344 23.7 KB

MY CUSTOMIZED GRID:

1
11133×399 24.2 KB

Thanks,

Alice

2

Just make sure that in the BAQ you set the “Like” property of these fields to be ShipHead.PackNum

3

Is there a way to limit the Open With ... items based on record content?

Two examples

  1. If a packer is marked SHIPPED, then only show the Tracker program.
  2. If the packer was created in another site, either:
    a. Don’t show any Open With ... entries (because you can’t open it from the current site)
    b. Have an Open With .. entry Customer Shipment Entry in <site> and open that form under that site.
4

Sure, but that requires customization.

5

Jose,

Its probably right in from of my face, but where do I set the “Like” property within the BAQ builder?

And as always, thank you for your help. :star_struck:

6

On the Display Fields tab there is a little button on the bottom left of that panel that says something like… Extended Properties (going from memmory)

But there, you can set the Like Property.

7

I think its called Advanced Column Editor maybe

(Edit - Calvin found it. It’s Field Attributes Editor)

8

This one?

image

3 Likes
9

That little guy, thanks @ckrusen! My Epicor is undergoing upgrade and I couldn’t login to look.

10

@josecgomez - The Customer Shipments and Misc Shipments use two entirely different tables (ShipHead and MscShpHd, respectively).

So the MscShpHd.PackNum field doesn’t really point to a ShipHead.PackNum record.

@Alice_Elizabeth - Are you sure your BAQ is using the right tables? There can be duplicate “packer numbers” within a company.

For example, I just made a new Misc Shipment, and is was assigned PackNum 25601 - the next available PackNum for Misc Shipments. Even though We already have a Customer Shipment with Packnum 25601.

image

1 Like
11

Correct so she must be either using the wrong table / record or the wrong Extended Props.

12

Got it!

image
image1039×654 32.9 KB

Thank you!

13

I made my test BAQ with a UNION subquery to join the results from ShipHead and MscShpHd, and even when a record is from the MscShpHd table, the Open With... treats it like it is a ShipHead Record.

image
image744×351 14.2 KB

I’m guessing this is because the Top query has the ShipHead table, and the UNION Query has the MscShpHd table.

But when I add a calc column of the PackNum (PkNum in my BAQ) to each query, and then set the LIKE property to each calc fields respective table, I get Open With ... Misc Shipment ... for records from either table.

image
image798×262 10.8 KB

1 Like
14

Did that column originally have a LIKE attribute? And was it on the MscShpHd table?

15

Yes, it was originally set to miscShpHd table.

16

Just curious as to why the PartTran_PackNum's LIKE property chose that table instead of the much more common ShipHead.

Does your BAQ have any of the MscShp tables in it?

17

Oddly, no. I would have thought that is would default to different “LIKE” property as well.

image
image785×398 13.9 KB