Sage 100

Todd you nailed it! Activity Log drill-down is the front-end for viewing all the export and import job logs!! When I saw the 90 Minds Sage Dev Roundatable recently, I saw that and confused it to mean it was coming in 2020 PU1, not realizing it was already in 2019. Works nice after filtering for V/I module. Interestingly, the last job log for imports is viewable directly in Import Job Maintenance using the Job Log button but in Export Job Maintenance "The Log Table is empty" appears (bug).

I had considered Perform Logic but they have around 50 exports and 20 imports so it seemed too much to manually add to each job. I could instead merge the Perform records into the Perform tables or just override VI_Export_UI and VI_Import_UI. I'll give them some options. I've never used mklink to do a symbolic link. I'll look into it!

On the last 90 Minds Sage Dev roundtable, Fred M talked about V/I enhancements coming for 2020 PU1 in Sept. 

• For import jobs, on Job Log display click new button to export failed records to TXT file saved to source file location folder (but not also emailed). Limited to imports of Delimited and ASCII type.
  (Good stuff but why a button instead of auto-run as that means it cannot run on auto-imports? Why hard-code location to source folder b/c that means you limited yourself to Delimited and ASCII? Why not email?  Quick wins are great but maybe this one shouldn't be half-baked. My own custom solution does all that. )
  
•  Job Log display to allow filtering
•  Job Log display to include original row / line from source file
• 3 additional V/I requests (unstated) from the Sweet 16 list.

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Thanks for sharing Brett. I'll vote / comment on your entry in the the Ideas site! BTW I think he meant filtering not deleting. I commented on it above in a previous reply.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------


Original Message:
Sent: 12-18-2020 13:08
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Thanks, @Alnoor Cassim, I actually did see where you mentioned that previously above and thought after-the-fact that it may have been related.

Thanks for sharing Brett. I'll vote / comment on your entry in the the Ideas site! BTW I think he meant filtering not deleting. I commented on it above in a previous reply.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:08
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Voted for it and added my comments. Thanks Brett! https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/40956

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA
------------------------------


Original Message:
Sent: 12-18-2020 13:45
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks, @Alnoor Cassim, I actually did see where you mentioned that previously above and thought after-the-fact that it may have been related.

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


Original Message:
Sent: 12-18-2020 13:26
From: Alnoor Cassim
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks for sharing Brett. I'll vote / comment on your entry in the the Ideas site! BTW I think he meant filtering not deleting. I commented on it above in a previous reply.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:08
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

• • A Setup menu has been added to the Visual Integrator module. Visual Integrator Options has been added to the menu.
  • In Visual Integrator Options you can manage the log files that are generated when running import and export jobs and when automatically scheduled jobs are run.
  • You can specify whether to reuse the existing log files when jobs are run or create new ones. You can also select the location where log files are saved.

Voted for it and added my comments. Thanks Brett! https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/40956

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:45
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks, @Alnoor Cassim, I actually did see where you mentioned that previously above and thought after-the-fact that it may have been related.

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


Original Message:
Sent: 12-18-2020 13:26
From: Alnoor Cassim
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks for sharing Brett. I'll vote / comment on your entry in the the Ideas site! BTW I think he meant filtering not deleting. I commented on it above in a previous reply.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:08
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

I just found out this resolution is also in v2020.2, of which I located the following in the v2020.2 Release Notes:  "Visual Integrator Job Log Report no longer defaults to print Logs for All existing Jobs.  DevID 112745 Knowledgebase ID 109111".  Apparently the changes made for this Res were fairly substantial and so it was decided to roll it into the next v2020 PU (.2 at the time) and v2021.

I've asked Sage to update the KB article, as currently for Resolution it shows "Sage Engineering is currently reviewing this issue".  And I've requested they update the Ideas site post to include that it was also fixed in v2020.2.

• • A Setup menu has been added to the Visual Integrator module. Visual Integrator Options has been added to the menu.
  • In Visual Integrator Options you can manage the log files that are generated when running import and export jobs and when automatically scheduled jobs are run.
  • You can specify whether to reuse the existing log files when jobs are run or create new ones. You can also select the location where log files are saved.

Voted for it and added my comments. Thanks Brett! https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/40956

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:45
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks, @Alnoor Cassim, I actually did see where you mentioned that previously above and thought after-the-fact that it may have been related.

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


Original Message:
Sent: 12-18-2020 13:26
From: Alnoor Cassim
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks for sharing Brett. I'll vote / comment on your entry in the the Ideas site! BTW I think he meant filtering not deleting. I commented on it above in a previous reply.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:08
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

I just found out this resolution is also in v2020.2, of which I located the following in the v2020.2 Release Notes:  "Visual Integrator Job Log Report no longer defaults to print Logs for All existing Jobs.  DevID 112745 Knowledgebase ID 109111".  Apparently the changes made for this Res were fairly substantial and so it was decided to roll it into the next v2020 PU (.2 at the time) and v2021.

I've asked Sage to update the KB article, as currently for Resolution it shows "Sage Engineering is currently reviewing this issue".  And I've requested they update the Ideas site post to include that it was also fixed in v2020.2.

• • A Setup menu has been added to the Visual Integrator module. Visual Integrator Options has been added to the menu.
  • In Visual Integrator Options you can manage the log files that are generated when running import and export jobs and when automatically scheduled jobs are run.
  • You can specify whether to reuse the existing log files when jobs are run or create new ones. You can also select the location where log files are saved.

Voted for it and added my comments. Thanks Brett! https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/40956

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:45
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks, @Alnoor Cassim, I actually did see where you mentioned that previously above and thought after-the-fact that it may have been related.

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


Original Message:
Sent: 12-18-2020 13:26
From: Alnoor Cassim
Subject: Any way to control Excessive V/I Log Files since v2019

Thanks for sharing Brett. I'll vote / comment on your entry in the the Ideas site! BTW I think he meant filtering not deleting. I commented on it above in a previous reply.

------------------------------
Alnoor Cassim

Email: alnoor@asifocus.com
Ph: 949-689-9887
Orange County, CA


Original Message:
Sent: 12-18-2020 13:08
From: Brett Zimmerman
Subject: Any way to control Excessive V/I Log Files since v2019

Response from Sage:  "After checking with my team I did confirm that there is currently no option to have VI logs omitted from records. I did fins however that logs can be filtered after being created with Sage 100 2020. I agree with you that VI logs can definitely get out of hand when imports are being run every hour, and believe there should be an option to turn logging off."

- I assume he meant "deleted" and not "filtered".

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


Original Message:
Sent: 06-01-2020 12:10
From: Wayne Schulz
Subject: Any way to control Excessive V/I Log Files since v2019

This is increasingly important as the small Sage 100 users depart due to never-ending price hikes. The remaining users are larger companies who do have these types of security concerns which means Sage needs to pay attention to these requests or risk losing portions of their remaining installed base.

And, please, for updates don't just throw a log file into a path where every Sage user is required to have full rights. At some point, an auditor is going to know the questions to ask and will inquire about who can access that folder and how likely it is that the log file could be erased, replaced, or modified.

I'm already seeing these types of questions on a regular basis which makes me think at some point the only realistic versions are Advanced and Premium which should allow for some safeguarding of data by virtue of service accounts/ SQL.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990