Formatting

[LTriska]

Hi.

When I generate a BOM, for example, the field TAGS and Description appears as attached (BOM_1).
I would like appear as attached (BOM_2).

How could I do this?

Thanks.

LTriska

[Anonymous]

There is not a supplied way to do this. The only way I can think of is a
user-post that would take the individual values and string them together as
one value. If you look at the supplied user post .lsp file it might give you
an idea on how to do this. I might be able to provide some assistance if you
want to try this route.

Pat Murnen

wrote in message news:6004640@discussion.autodesk.com...
Hi.

When I generate a BOM, for example, the field TAGS and Description appears
as attached (BOM_1).
I would like appear as attached (BOM_2).

How could I do this?

Thanks.

LTriska

[LTriska]

Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[Anonymous]

Do you want to look at the one supplied and see if you can write this
yourself? If not and you want me to help it probably would be next week
before I could look at it. Just let me know.

Pat Murnen

wrote in message news:6006432@discussion.autodesk.com...
Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[Anonymous]

I have modifed the bom.lsp and bom.dcl to provide a 4th option that
concatenates the Tags and Description fields. The first 3 options were
already defined as some other function.

The Description one might need some changing due to the way it is built.
This field is built on-the-fly from a set of possible fields. The user post
has no way of knowing which ones you are including so I have included them
all. You might need to go in and take some out if you do not want them
included. I have included some comments in the .lsp file that should make
that easier.

One thing to note is that the Description field is actually built up of
separate fields. So if you don't want to modify them to be one field with
the commas as your image showed, you could just remove the Description field
from the report and add in each individual field, i.e. MISC1, MISC2, etc.
This is done on the Change Report Format disloag selected from the Report
Generator. (if you do this you would need to remove some of the code in the
user post).

One other thing to note is that the BOM report can use 4 different possible
user post files depending on the selected display option. The fields may be
in different order so the same user post might not work for each option. The
one I modified is for the Normal Tallied.

Schematic BOM - 4 options depending on the Display option selected
1) BOM.LSP = Normal tallied
2) BOM_LOC.LSP = Normal tallied (grouped by Installation/Location)
3) PUR_BOM.LSP = Tallied Purchase List
4) TAG_BOM.LSP = By Tag


Panel BOM - 4 options depending on the Display option selected
1) BOMPNL.LSP
2) PBOM_LOC.LSP
3) PUR_PBOM.LSP
4) TAG_PBOM.LSP

Let me know if this doesn't do what you wanted.
Pat Murnen

wrote in message news:6006432@discussion.autodesk.com...
Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[LTriska]

Hi.

I will do the tests.

Thanks.

LTriska

[Anonymous]

Hi!

See if I did it right:
I pasted the BOM.DCL and BOM.LSP in the following folder: C:\Documents and
Settings\All Users\Documentos\Autodesk\Acade 2009\Support.
I run Schematic Reports command > BOM > Normal Tallied Format, but continues
the same thing.
What am I doing wrong?

Thanks.

LTriska

"Pat Murnen" escreveu na mensagem
news:6008926@discussion.autodesk.com...
I have modifed the bom.lsp and bom.dcl to provide a 4th option that
concatenates the Tags and Description fields. The first 3 options were
already defined as some other function.

The Description one might need some changing due to the way it is built.
This field is built on-the-fly from a set of possible fields. The user post
has no way of knowing which ones you are including so I have included them
all. You might need to go in and take some out if you do not want them
inc
luded. I have included some comments in the .lsp file that should make
that easier.

One thing to note is that the Description field is actually built up of
separate fields. So if you don't want to modify them to be one field with
the commas as your image showed, you could just remove the Description field
from the report and add in each individual field, i.e. MISC1, MISC2, etc.
This is done on the Change Report Format disloag selected from the Report
Generator. (i
f you do this you would need to remove some of the code in the
user post).

One other thing to note is that the BOM report can use 4 different possible
user post files depending on the selected display option. The fields may be
in different order so the same user post might not work for each option. The
one I modified is for the Normal Tallied.

Schematic BOM - 4 options depending on the Display option selected
1) BOM.LSP = Normal tallied
2) BOM_LOC.LSP = Normal talli
ed (grouped by Installation/Location)
3) PUR_BOM.LSP = Tallied Purchase List
4) TAG_BOM.LSP = By Tag


Panel BOM - 4 options depending on the Display option selected
1) BOMPNL.LSP
2) PBOM_LOC.LSP
3) PUR_PBOM.LSP
4) TAG_PBOM.LSP

Let me know if this doesn't do what you wanted.
Pat Murnen

wrote in message news:6006432@discussion.autodesk.com...
Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[Anonymous]

After you run the report you need to select the User Post button on the
Report Generator dialog. Then select which post-processing option you want
to run on the data.

Pat Murnen

"LTriska" wrote in message
news:6014848@discussion.autodesk.com...
Hi!

See if I did it right:
I pasted the BOM.DCL and BOM.LSP in the following folder: C:\Documents and
Settings\All Users\Documentos\Autodesk\Acade 2009\Support.
I run Schematic Reports command > BOM > Normal Tallied Format, but continues
the same thing.
What am I doing wrong?

Thanks.

LTriska

"Pat Murnen" escreveu na mensagem
news:6008926@discussion.autodesk.com...
I have modifed the bom.lsp and bom.dcl to provide a 4th option that
concatenates the Tags and Description fields. The first 3 options were
already defined as some other function.

The Description one might need some changing due to the way it is built.
This field is built on-the-fly from a set of possible fields. The user post
has no way of knowing which ones you are including so I have included them
all. You might need to go in and take some out if you do not want them
inc
luded. I have included some comments in the .lsp file that should make
that easier.

One thing to note is that the Description field is actually built up of
separate fields. So if you don't want to modify them to be one field with
the commas as your image showed, you could just remove the Description field
from the report and add in each individual field, i.e. MISC1, MISC2, etc.
This is done on the Change Report Format disloag selected from the Report
Generator. (i
f you do this you would need to remove some of the code in the
user post).

One other thing to note is that the BOM report can use 4 different possible
user post files depending on the selected display option. The fields may be
in different order so the same user post might not work for each option. The
one I modified is for the Normal Tallied.

Schematic BOM - 4 options depending on the Display option selected
1) BOM.LSP = Normal tallied
2) BOM_LOC.LSP = Normal talli
ed (grouped by Installation/Location)
3) PUR_BOM.LSP = Tallied Purchase List
4) TAG_BOM.LSP = By Tag


Panel BOM - 4 options depending on the Display option selected
1) BOMPNL.LSP
2) PBOM_LOC.LSP
3) PUR_PBOM.LSP
4) TAG_PBOM.LSP

Let me know if this doesn't do what you wanted.
Pat Murnen

wrote in message news:6006432@discussion.autodesk.com...
Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[Anonymous]

Hi!

I did everything less this.

You helped me a lot.

Thank you very much.

LTriska

"Pat Murnen" escreveu na mensagem
news:6015093@discussion.autodesk.com...
After you run the report you need to select the User Post button on the
Report Generator dialog. Then select which post-processing option you want
to run on the data.

Pat Murnen

"LTriska" wrote in message
news:6014848@discussion.autodesk.com...
Hi!

See if I did it right:
I pasted the BOM.DCL and BOM.LSP in the following folder: C:\Documents and
Settings\All Users\Documentos\Autodesk\Acade 2009\Support.
I run Schematic Reports command > BOM > Normal Tallied Format, but continues
the same thing.
What am I doing wrong?

Thanks.

LTriska

"Pat Murnen" escreveu na mensagem
news:6008926@discussion.autodesk.com...
I have modifed the bom.lsp and bom.dcl to provide a 4th option that
concatenates the Tags and Description fields. The first 3 options were
already defined as some other function.

The Description one might need some changing due to the way it is built.
This field is built on-the-fly from a set of possible fields. The user post
has no way of knowing which ones you are including so I have included them
all. You might need to go in and take some out if you do not want them
inc
luded. I have included some comments in the .lsp file that should make
that easier.

One thing to note is that the Description field is actually built up of
separate fields. So if you don't want to modify them to be one field with
the commas as your image showed, you could just remove the Description field
from the report and add in each individual field, i.e. MISC1, MISC2, etc.
This is done on the Change Report Format disloag selected from the Report
Generator. (i
f you do this you would need to remove some of the code in the
user post).

One other thing to note is that the BOM report can use 4 different possible
user post files depending on the selected display option. The fields may be
in different order so the same user post might not work for each option. The
one I modified is for the Normal Tallied.

Schematic BOM - 4 options depending on the Display option selected
1) BOM.LSP = Normal tallied
2) BOM_LOC.LSP = Normal talli
ed (grouped by Installation/Location)
3) PUR_BOM.LSP = Tallied Purchase List
4) TAG_BOM.LSP = By Tag


Panel BOM - 4 options depending on the Display option selected
1) BOMPNL.LSP
2) PBOM_LOC.LSP
3) PUR_PBOM.LSP
4) TAG_PBOM.LSP

Let me know if this doesn't do what you wanted.
Pat Murnen

wrote in message news:6006432@discussion.autodesk.com...
Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[Anonymous]

No problem. I hope the user post does what you need.

Pat Murnen

"LTriska" wrote in message
news:6015160@discussion.autodesk.com...
Hi!

I did everything less this.

You helped me a lot.

Thank you very much.

LTriska

"Pat Murnen" escreveu na mensagem
news:6015093@discussion.autodesk.com...
After you run the report you need to select the User Post button on the
Report Generator dialog. Then select which post-processing option you want
to run on the data.

Pat Murnen

"LTriska" wrote in message
news:6014848@discussion.autodesk.com...
Hi!

See if I did it right:
I pasted the BOM.DCL and BOM.LSP in the following folder: C:\Documents and
Settings\All Users\Documentos\Autodesk\Acade 2009\Support.
I run Schematic Reports command > BOM > Normal Tallied Format, but continues
the same thing.
What am I doing wrong?

Thanks.

LTriska

"Pat Murnen" escreveu na mensagem
news:6008926@discussion.autodesk.com...
I have modifed the bom.lsp and bom.dcl to provide a 4th option that
concatenates the Tags and Description fields. The first 3 options were
already defined as some other function.

The Description one might need some changing due to the way it is built.
This field is built on-the-fly from a set of possible fields. The user post
has no way of knowing which ones you are including so I have included them
all. You might need to go in and take some out if you do not want them
inc
luded. I have included some comments in the .lsp file that should make
that easier.

One thing to note is that the Description field is actually built up of
separate fields. So if you don't want to modify them to be one field with
the commas as your image showed, you could just remove the Description field
from the report and add in each individual field, i.e. MISC1, MISC2, etc.
This is done on the Change Report Format disloag selected from the Report
Generator. (i
f you do this you would need to remove some of the code in the
user post).

One other thing to note is that the BOM report can use 4 different possible
user post files depending on the selected display option. The fields may be
in different order so the same user post might not work for each option. The
one I modified is for the Normal Tallied.

Schematic BOM - 4 options depending on the Display option selected
1) BOM.LSP = Normal tallied
2) BOM_LOC.LSP = Normal talli
ed (grouped by Installation/Location)
3) PUR_BOM.LSP = Tallied Purchase List
4) TAG_BOM.LSP = By Tag


Panel BOM - 4 options depending on the Display option selected
1) BOMPNL.LSP
2) PBOM_LOC.LSP
3) PUR_PBOM.LSP
4) TAG_PBOM.LSP

Let me know if this doesn't do what you wanted.
Pat Murnen

wrote in message news:6006432@discussion.autodesk.com...
Hi!

I would like to use this LSP routine.

Thanks.

LTriska

[LTriska]

Hi!

The LSP routine worked but the fields CATALOG and MFG were for the column DESCRIPTION, see the attached.

How could I solve this?

Thanks.

LTriska

[Anonymous]

You need to modify the function so it doesn't include the Catalog and Mfg
fields.

Some comments at the top of the .lsp file indicate the order of the data.
; Each sublist within wd_rdata list of lists:
; nth 0=ITEM
; nth 1=QTY
; nth 2=SUBQTY
; nth 3=CAT
; nth 4=MFG
; nth 5=
; nth 6=
; nth 7=CAT DESC
; nth 8=QUERY2
; nth 9=QUERY3
; nth 10=MISC1
; nth 11=MISC2
; nth 12=USER1
; nth 13=USER2
; nth 14=USER3

Here is some of the code in the function I added.

(foreach ii (list 4 3 7 8 9 10 11 12 13 14)
(setq val (nth ii lst))
(if (AND val (/= val ""))
(progn
; blank this value out
(setq lst (wd_nth_subst ii "" lst))
; add to running string
(if (/= str "")
(setq str (strcat str "," val)) ; 2+ so add comma
(setq str val) ; first one
)
) )
)
The list where I have the numbers, i.e. (list 4 3 7 8 9 10 11 12 13 14),
those are all the possible fields the might go into making up the
concatenated description. You need to take out any of the fields that you do
not want. So if you do not want Catalog and Manufacturer as part of this big
decription then edit the .lsp file and take out the 3 & 4. (use something
like NotePad) So the result would look like this -

(foreach ii (list 7 8 9 10 11 12 13 14)
(setq val (nth ii lst))
(if (AND val (/= val ""))
(progn
; blank this value out
(setq lst (wd_nth_subst ii "" lst))
; add to running string
(if (/= str "")
(setq str (strcat str "," val)) ; 2+ so add comma
(setq str val) ; first one
)
) )
)

If you didn't want to include MISC1 & MISC2 then you would take out 10 & 11.

You can also change the order of the data in your concatenated line by
changing the order of the numbers in that list. Say you wanted the order
USER1, USER2, USER3, CAT DESC. Then the list would look like (list 12 13 14
7)

Hope this helps,
Pat Murnen


wrote in message news:6017048@discussion.autodesk.com...
Hi!

The LSP routine worked but the fields CATALOG and MFG were for the column
DESCRIPTION, see the attached.

How could I solve this?

Thanks.

LTriska

[Anonymous]

Hi, Pat Murnen!

It was exactly this what I needed.

Again, thank you very much.

LTriska

"Pat Murnen" escreveu na mensagem
news:6017069@discussion.autodesk.com...
You need to modify the function so it doesn't include the Catalog and Mfg
fields.

Some comments at the top of the .lsp file indicate the order of the data.
; Each sublist within wd_rdata list of lists:
; nth 0=ITEM
; nth 1=QTY
; nth 2=SUBQTY
; nth 3=CAT
; nth 4=MFG
; nth 5=
; nth 6=
; nth 7=CAT DESC
; nth 8=QUERY2
; nth 9=QUERY3
; nth 10=MISC1
; nth 11=MISC2
; nth 12=USER1
; nth 13=USER2
; nth 14=USER3

Here is some of the code in the function I added.

(foreach ii (list 4 3 7 8 9 10 11 12 13 14)
(setq val (nth ii lst))
(if (AND val (/= val ""))
(progn
; blank this value out
(setq lst (wd_nth_subst ii "" lst))
; add to running string
(if (/= str "")
(setq str (strcat str "," val)) ; 2+ so add comma
(setq str val) ; first one
)
) )
)
The list where I have the numbers, i.e. (list 4 3 7 8 9 10 11 12 13 14),
those are all the possible fields the might go into making up the
concatenated description. You need to take out any of the fields that you do
not want. So if you do not want Catalog and Manufacturer as part of this big
decription then edit the .lsp file and take out the 3 & 4. (use something
like NotePad) So the result would look like this -

(foreach ii (list 7 8 9 10 11 12 13 14)
(setq val (nth ii lst))
(if (AND val (/= val ""))
(progn
; blank this value out
(setq lst (wd_nth_subst ii "" lst))
; add to running string
(if (/= str "")
(setq str (strcat str "," val)) ; 2+ so add comma
(setq str val) ; first one
)
) )
)

If you didn't want to include MISC1 & MISC2 then you would take out 10 & 11.

You can also change the order of the data in your concatenated line by
changing the order of the numbers in that list. Say you wanted the order
USER1, USER2, USER3, CAT DESC. Then the list would look like (list 12 13 14
7)

Hope this helps,
Pat Murnen


wrote in message news:6017048@discussion.autodesk.com...
Hi!

The LSP routine worked but the fields CATALOG and MFG were for the column
DESCRIPTION, see the attached.

How could I solve this?

Thanks.

LTriska

[Anonymous]

No problem.

Pat

"LTriska" wrote in message
news:6017290@discussion.autodesk.com...
Hi, Pat Murnen!

It was exactly this what I needed.

Again, thank you very much.

LTriska

"Pat Murnen" escreveu na mensagem
news:6017069@discussion.autodesk.com...
You need to modify the function so it doesn't include the Catalog and Mfg
fields.

Some comments at the top of the .lsp file indicate the order of the data.
; Each sublist within wd_rdata list of lists:
; nth 0=ITEM
; nth 1=QTY
; nth 2=SUBQTY
; nth 3=CAT
; nth 4=MFG
; nth 5=
; nth 6=
; nth 7=CAT DESC
; nth 8=QUERY2
; nth 9=QUERY3
; nth 10=MISC1
; nth 11=MISC2
; nth 12=USER1
; nth 13=USER2
; nth 14=USER3

Here is some of the code in the function I added.

(foreach ii (list 4 3 7 8 9 10 11 12 13 14)
(setq val (nth ii lst))
(if (AND val (/= val ""))
(progn
; blank this value out
(setq lst (wd_nth_subst ii "" lst))
; add to running string
(if (/= str "")
(setq str (strcat str "," val)) ; 2+ so add comma
(setq str val) ; first one
)
) )
)
The list where I have the numbers, i.e. (list 4 3 7 8 9 10 11 12 13 14),
those are all the possible fields the might go into making up the
concatenated description. You need to take out any of the fields that you do
not want. So if you do not want Catalog and Manufacturer as part of this big
decription then edit the .lsp file and take out the 3 & 4. (use something
like NotePad) So the result would look like this -

(foreach ii (list 7 8 9 10 11 12 13 14)
(setq val (nth ii lst))
(if (AND val (/= val ""))
(progn
; blank this value out
(setq lst (wd_nth_subst ii "" lst))
; add to running string
(if (/= str "")
(setq str (strcat str "," val)) ; 2+ so add comma
(setq str val) ; first one
)
) )
)

If you didn't want to include MISC1 & MISC2 then you would take out 10 & 11.

You can also change the order of the data in your concatenated line by
changing the order of the numbers in that list. Say you wanted the order
USER1, USER2, USER3, CAT DESC. Then the list would look like (list 12 13 14
7)

Hope this helps,
Pat Murnen


wrote in message news:6017048@discussion.autodesk.com...
Hi!

The LSP routine worked but the fields CATALOG and MFG were for the column
DESCRIPTION, see the attached.

How could I solve this?

Thanks.

LTriska

[evanj666]

Please help me in regards the bom_loc.lsp

Topic: bom_loc - User Post
http://discussion.autodesk.com/forums/thread.jspa?threadID=749477