Recent Posts

Pages: [1] 2 3 ... 10
1
Activant/Prelude Support / Re: Conversion needed
« Last post by precisonline on August 07, 2017, 11:26:44 am »
Tom that's awfully clever.  I don't know that I can improve upon it without writing some code.  We're really talking about an input conversion, right?  You want the value stored with the extra zeroes right?
2
Activant/Prelude Support / Re: Conversion needed
« Last post by Tom Pellitieri on August 01, 2017, 02:06:50 pm »
I tried "MR#%3" which gave me these results:

1 -> " 001"
12 -> " 012"
123 -> " 123"
1234 -> "1234"
12345 -> "2345"

Note that there is a leading space, but you should be able to trim that out.
3
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by precisonline on July 31, 2017, 06:57:00 pm »
Sounds like a fantastic solution.
4
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by DonQuixote on July 31, 2017, 06:42:26 pm »
They finally accepted the fact that lines number were unique but complicated the situation by making me replace kits with the kit parts.  My solution was to use the line number and .1, .2, .3... for the kit part positions.   :o
5
Activant/Prelude Support / Conversion needed
« Last post by DonQuixote on July 31, 2017, 06:38:50 pm »
I need a conversion that will work in the dictionary and in a screen that will zero fill 3 digits but accepts and display a length of 4.
The purpose is that we expanded our territories to four digits but we still have many 3 digit territories.
So if a person enters  "1"  then "001" will be displayed and used to read the TERR file
If you enter "1024" then it will display "1024" and read the TERR file.

The old conversion "MR%3" does not work because it cuts the length to 3 digits; so that 1024 become 024.
Using "MR%4" does not work because "1" becomes "0001" and is invalid because we want "001".



6
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by precisonline on July 20, 2017, 03:52:09 pm »
Why not use the line sequence instead; that is, the line number that appears in /SOE?  I would load up the order header, locate the key in <200.M>, and use that position.
7
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by DonQuixote on July 20, 2017, 03:49:49 pm »
I've been asked to extract data for each order line but using the Customer Line number instead of the Order's line number.  But, that isn't unique and that's the issue.  To keep it unique the user has to understand I need to use the order line number and live with the fact it doesn't reference the Customer's line number.   :-X
8
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by precisonline on July 20, 2017, 03:37:16 pm »
I think it's just there as a convenience.  How are you wanting to use it?
9
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by DonQuixote on July 20, 2017, 03:33:04 pm »
 :-\   Maybe.  I just don't have control over that number and its all dependent on the order of entry. 
10
Activant/Prelude Support / Re: CUST.LN.NUM in the ORDER.HISTORY file
« Last post by precisonline on July 20, 2017, 03:26:39 pm »
Is that a concern?  If I had one P/O with one line on it and I typed it into Prelude over 12 order lines, wouldn't I want all 12 to point back to the same line number on the P/O?
Pages: [1] 2 3 ... 10