Bartender labels

Kinetic ERP
1

I have an epicor function that generates a text file for my bartender labels. My problem is I don’t know the right path to the drop file since we are hosted in the cloud. Help Please.

string printer = "PPL2";
string BTWFile = Ice.Lib.PathHelper.GetFolderPath(Epicor.ServiceModel.Utilities.SpecialFolder.CompanyData) + @"\BARTENDER\Labels\Part Labels Short.BTW";
string part = this.PartNum;
string outputPath = Ice.Lib.PathHelper.GetFolderPath(Epicor.ServiceModel.Utilities.SpecialFolder.CompanyData) + @"\BARTENDER\Print\";
string COMMA = "\",\"";
string BTFile = outputPath + "PartLabel_" + DateTime.Now.ToString("yyyyMMdd_HHmmssfff") + ".BT";
try
{
  string header = "%BTW% /AF=\"" + BTWFile + "\" /D=\"<Trigger File Name>\" /PRN=\"" + printer + "\" /DBTEXTHEADER=3 /C=1 /R=3 /P " + Environment.NewLine;
  header += @"%END%" + Environment.NewLine;
  string line = "\"" + "PartNum" + COMMA + "PartDescription" + "\"" + Environment.NewLine;
  line += "\"" + PartNum + COMMA + PartDescription + "\"";
  System.IO.File.WriteAllText(BTFile, header + line);
}
catch (Exception exception)
{
  this.ex = exception.Message + "\n" + exception.InnerException;
}
1 Like
2

The BTWFle and outputpath are not correc.

3

Did you get the PowerShell script from Epicor? If not, you will have to submit an EpicCare ticket.

Otherwise you may have to check your format for the Report Style. This is what I have that works for us.

Report Location: \\Bartender Drive From Epicor\Location of Report
Output Location: //Bartender Drive From Epicor/Output of files

4

I found the path in the script and put it in my code and now I get an access denied error

System.IO.IOException: Permission denied

1 Like
5

I am getting the same issue right now in Pilot. I have submitted a ticket for it and the guy seemed to know the problem. This happened on the upgrade last week but he didn’t think it was from the Linux part of the update. No PRB yet.

It does work in live for me correctly but not in the Pilot.

Edit: If you want to reference, my case number is CS0005315999

1 Like
6

As @tsimon mentioned it’s likely due to the switch to Linux last week.

2 Likes
7

Are you having this issue in your Pilot database? If so could be they moved your Pilot to Linux containers. We’re hit with the same issue.

3 Likes
8

Chiming in here to say the same… Pilot and Third cannot access Azure File Share. Production works though.

3 Likes
9

Same for us and no response yet from my ticket I logged Friday. :man_facepalming: :dumpster_fire:

1 Like
10

I received a response today asking what the azure file path was and if it was configured by Epicor. I replied and confirmed but haven’t heard anything back yet.

1 Like
11

Latest recommendation on our ticket was to disable the directive and re-test. Kinda defeats the purpose if the failure point is a label function that we need to work, right? It’s gonna be an exceptionally stellar week.

1 Like
12

:man_facepalming: :roll_eyes:

1 Like
13

what-are

2 Likes
14

Silly response I know, but I bet it will complete if you do so. Mine does. Then it won’t let you put the share back in and save (lol oops). Tells me that it can’t communicate with the Azure File Share properly.

Edit: sorry, not disable the entire directive. Just remove the Azure File Share path in the Output Path section in Report Styles.

15

I’m sure it will “fix” it. But that’s not a fix. They likely have to add/change something in the BPM code like they did when Workato made a change. That requires a hot fix or new version of Kinetic. Hopefully they figure it out before they push prod onto Linux.

16

It’s not just bartender labels, EDI docs are erroring too. So probably anything that tries to write to that share.

17

Yuuuuuuuuup…writing to and reading from.

18

Most likely.

19

Amazing.

Recent workarounds include ‘try again’ and ‘don’t do it at all’

3 Likes
20

I can’t believe no one at Epicor tested printing labels. Or tested really anything that involved saving files. Another failure.