@Andrew D'Antonio That’s what we are doing now, just looking for a way to generate both ahead of time, thanks!
To follow up, we asked hosting to update the configuration to Office 2003, but this did not change the issue when running reports through the batch manager. Short of reconfiguring our current reports that are run this way, do you have any other suggestions? We have also confirmed with IT department that the reports cannot be converted, we receive corruption errors when opening as xlsx docs.
Unfortunately, I do not have these options under Configuration Editor, maybe that’s because we are hosted?
@Christophe Thank you, I had not linked the activity code!
Hi @Phil Seifert , We are not even getting to where we can access the view and we do not have access to our DB. It does work after deactivating the customization. We’ve recreated the screens a couple of times now (both in web and back office) and it goes back to the same spinning wheel after saving. When we unpublish in the customizer manager, we get the following. I’m going to need further direction on how to see the event viewer logs if they are available to me.
Hi @Phil Seifert , We are exporting from the report view, not a QBE, that’s causing differences.
Sure, this one shows where the part number is clipped on the batchmgr version, but not on the version run manually. This issue is also the one where some users see the clipped version, others do not. This one shows where the columns export differently based on whether the batch scheduler is used or not.
When I choose Save As, it populates as a .txt file… which is different than what we are used to. Usually, if I choose to save as a .csv file, the result is in spreadsheet form. So, you might be on to something…but I’m not sure how to fix it. No funny characters or foreign languages in the file, and yes, all batch parameters are the same with exception of report name and output addresses.
Good morning,The report was created through Customizer. Each report runs on its own batch schedule. The only difference in the batch parameters is who the attachment is sent to. Even when it is just sent to my own address, it is not producing the same results as when run manually.Within the report, the customer/warehouse is different. But since the report runs fine when run manually, I don’t think that is the issue.This is a view of the report run manually. Same report, same day - below is what was sent for the scheduled report.
Hi @Phil Seifert , It is a custom report that we have developed. However, we have multiple versions running of this report (for different customers/accounts) and all are running fine except for one version of it. We’ve tried using different users to schedule thinking that might be the issue as well, however, even when I as customizer schedule it, we get these same results.
@Phil Seifert , We did some more testing and bypassing the warehouse security did not change results for the users. However, bypassing node security DID allow them to see all orders. So I’m still at a loss, we confirmed that orders not seen in results have the same node assignment as the users, the users all have access to that node. The report itself doesn’t address node in any way. It is tied to a specific warehouse, which is also set to the same node. Thoughts?
It’s a report internally created, HFT Receiving Report. Not a QBE, and nodes are set the same for both customer/site and all users. We did notice that those of us that can see the additional lines are set to bypass security and/or customizer. Looking into whether the order itself might be missing node information. Any other suggestions are welcome.
@Phil Seifert , Thank you, that did seem to trigger the restart of the individual jobs, but they seem to be getting stuck in the same place. I opened a support ticket on this yesterday, so I will request an IISRESET there.
Thanks Phil, It doesn’t like me pasting the text here, but this is what it says: If I need to email you the text directly, let me know.
Hi Phil, We are hosted, so I’m unsure about whether the attachments were copied. We can see all our attachments, so my guess is yes. We have tried uploading a new file, but it reacted the same way and does not show in the image section.Thanks.
No, we were able to see it in the circled section. The section is still there, but does not show the image.
We have discovered the issue… previously, we would turn the Print Pick List toggle on and choose Save to print one copy. The print date/time would update immediately confirming the print. Currently, when the Print Pick List toggle is turned on and choose Save, the document prints 1 copy. However, the print date/time does not update. If the Pick screen is refreshed, the print date/time appears at that time. When the Pick tab is closed, we receive the “do you want to save your changes?” popup (although previously saved). Choosing yes causes the document to print again. We have made our administrators aware of how it is functioning, but is a pain for them to use a workaround to prevent multiple prints. I believe the root issue lies with the Save button on the Pick module.
I exported the customized screens from PROD, published in UAT and reimported back to PROD. The error remains on these two screens (all we can find at the moment so this may have resolved a few) - Sales Order - priority not defined and Order Locator - cst_drop_down_test not defined. We don’t use the custom field at all.
I thought so too. I asked why I could see those in Production after this update when I’ve never been able to before. I was told that’s standard Customizer actions. I don’t want to publish what I have in UAT because some of them are not ready for Production. I deleted the DEV screens in Production the first time around. Any other suggestions?
I only have that option in UAT, not in Production.
This may be where I went wrong right after the update. I reran Conflict Resolver. I now have a list of screens in the DEV environment under Customizer Manager. I don’t have a way (or know how) to publish these. What is my next step?
Thanks Phil, We do find that the serial numbers are not displayed on the page after save. It’s usually very random… one line on page 14, two on page 18, etc. Just finding those lines that are blank usually takes some time and for each line, we have to scan all the serials to find the ones that weren’t captured. We are open to having an import developed if that would help, our team is already scanning all serials into a spreadsheet in addition to the system because of this issue. Thanks for your thoughts on the pop-up, I understand what you’re saying.
Thanks @Phil Seifert , that did fix the missing flush cache issue!
Our contracts are defined at the object of service level, the item is on contract and using SLA I showed you… however, they are defined as service in the contract category, both in the header and OOS. They need to be defined this way for other reasons, but is another line or contract required that is defined as repair for these settings to work as I’m expecting them to?
I thought so too, but it doesn’t seem to change the fix date. Is there another date field these options update? Or are there specific fields within the service level template that drive this? We currently have them set as below thinking the repair shop time should make this calculation.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
