Sage 100

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------

Extended descriptions are not intended to be managed separately from the normal description field... they are just the overflow, if the description runs long.

Did you try to pad what you want as the regular description to 30 characters?

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area

Thanks, @Kevin Moyes.  I have not tried the PAD function, but is that really possible in this case since we can't touch the reg desc and ext desc separately?

Extended descriptions are not intended to be managed separately from the normal description field... they are just the overflow, if the description runs long.

Did you try to pad what you want as the regular description to 30 characters?

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area

I wasn't referring to the function... just a potential strategy for manipulating the source data:

Thanks, @Kevin Moyes.  I have not tried the PAD function, but is that really possible in this case since we can't touch the reg desc and ext desc separately?

Extended descriptions are not intended to be managed separately from the normal description field... they are just the overflow, if the description runs long.

Did you try to pad what you want as the regular description to 30 characters?

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area

Ooooh, I think that might work, and be better than having to fix the 4,000 items with a carriage return in the first 30char. 

Hey btw, @Kevin Moyes, what's the big idea including pipes in your above sample?  You were the one who previously steered me away from pipe (on multiple occassions), and use a carat instead.  :)

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area
------------------------------


Original Message:
Sent: 05-21-2026 11:14
From: Kevin Moyes
Subject: VI import of items with extended desc

I wasn't referring to the function... just a potential strategy for manipulating the source data:

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-21-2026 10:38
From: Brett Zimmerman
Subject: VI import of items with extended desc

Thanks, @Kevin Moyes.  I have not tried the PAD function, but is that really possible in this case since we can't touch the reg desc and ext desc separately?

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 05-21-2026 09:53
From: Kevin Moyes
Subject: VI import of items with extended desc

Extended descriptions are not intended to be managed separately from the normal description field... they are just the overflow, if the description runs long.

Did you try to pad what you want as the regular description to 30 characters?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-21-2026 09:12
From: Brett Zimmerman
Subject: VI import of items with extended desc

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area

Your linked example in the top post used "|" as the separator... so it was fresh in my mind when typing that out. 

Yes, it is best to avoid this character in VI jobs because it messes up the VI job maintenance column settings on screen. 

"^" is better for sure.

Ooooh, I think that might work, and be better than having to fix the 4,000 items with a carriage return in the first 30char. 

Hey btw, @Kevin Moyes, what's the big idea including pipes in your above sample?  You were the one who previously steered me away from pipe (on multiple occassions), and use a carat instead.  :)

I wasn't referring to the function... just a potential strategy for manipulating the source data:

Thanks, @Kevin Moyes.  I have not tried the PAD function, but is that really possible in this case since we can't touch the reg desc and ext desc separately?

Extended descriptions are not intended to be managed separately from the normal description field... they are just the overflow, if the description runs long.

Did you try to pad what you want as the regular description to 30 characters?

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area

So you are recommending putting the carat before the stick?

So how do you save an Excel tile as text with the Carat separator?

------------------------------
Jeff Schwenk
Owner
Bottomline Software, Inc.
Waynesboro VA
(540) 221-4444

Improving bottom lines for over 25 years!
------------------------------


Original Message:
Sent: 05-21-2026 11:59
From: Kevin Moyes
Subject: VI import of items with extended desc

Your linked example in the top post used "|" as the separator... so it was fresh in my mind when typing that out. 

Yes, it is best to avoid this character in VI jobs because it messes up the VI job maintenance column settings on screen. 

"^" is better for sure.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-21-2026 11:54
From: Brett Zimmerman
Subject: VI import of items with extended desc

Ooooh, I think that might work, and be better than having to fix the 4,000 items with a carriage return in the first 30char. 

Hey btw, @Kevin Moyes, what's the big idea including pipes in your above sample?  You were the one who previously steered me away from pipe (on multiple occassions), and use a carat instead.  :)

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 05-21-2026 11:14
From: Kevin Moyes
Subject: VI import of items with extended desc

I wasn't referring to the function... just a potential strategy for manipulating the source data:

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-21-2026 10:38
From: Brett Zimmerman
Subject: VI import of items with extended desc

Thanks, @Kevin Moyes.  I have not tried the PAD function, but is that really possible in this case since we can't touch the reg desc and ext desc separately?

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area


Original Message:
Sent: 05-21-2026 09:53
From: Kevin Moyes
Subject: VI import of items with extended desc

Extended descriptions are not intended to be managed separately from the normal description field... they are just the overflow, if the description runs long.

Did you try to pad what you want as the regular description to 30 characters?

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 05-21-2026 09:12
From: Brett Zimmerman
Subject: VI import of items with extended desc

Although I have the carriage returns working in the extended desc, the issue here is when a carriage return/line break is present within the first 30char of the item desc, which the system does allow you to enter in that manner manually.

------------------------------
Brett Zimmerman
Net at Work
Greater Boston Area