Apologies for the delay here, but I think I’ve found a workaround while our engineering team works to get this resolved. I’ve built out a test case and the ticket thread is in their hands, and they’re aware of the issue.
Here’s the workaround that I used to generate a successful order in your system just a few minutes ago:
I went into one of the quotes I tested yesterday that reproduced this issue. You’ll see in the screenshot below that the quote has the same ‘One or more quote worksheets are still loading’.
On that same quote I clicked the Quoting Tools+ dropdown option on the lefthand navigation menu, and selected the ‘Clone Quote’ option there.
Once I cloned the quote and I went to the commit to order screen the alert was no longer there indicating that the quote worksheet needed to be created.
I committed the ‘Cloned Quote’ over to an order without any issues:
The workaround here is to generate the quote like you’ve been doing, but once you’ve generated the quote you’ll need to ‘Clone’ the quote. Once the cloned quote is generated you’ll see the issue you’ve been running into is no longer there.
You’ll then need to delete the original quote you created (so you don’t have an influx of quotes that you can’t commit). This will at least give you the ability to generate those production orders while we work diligently to get this resolved for you as quickly as possible.
I’ll bump our engineering team again to see if there are any updates right now. Please let me know if you have any questions here.
Just to confirm this was not done in your live environment, this was done in a backup of ours that was having the same issue you reported.
Please let me know if that workaround is a suitable measure that you can take to get those orders in your system to continue production.
I’ve bumped the ticket that’s in our engineering team’s hands for an update on potential resolutions in place. I’ll also be in touch with an update once that’s been sent my way.
I have tried your workaround.
I do not get that to work, I still receive the INTERNAL SERVER ERROR.
I might be missing some step or maybe i did something diffrent from you.
Just to clarify
On the first step did you only create the quote or did you press commit to order once?
Did you hit the create subassemblies on the first quote before you cloned it? or how did you get the “One or more quote worksheets are still loading” are still loading?
As soon as i hit create subassemblies I get internal server error.
So the only possibility for me to get to that stage you are describing is to hit back in the browser and then I get the view with the message “One or more quote worksheets are still loading”.
Is that where you cloned the quote from?
I should stress that enginering must USE FIGQWEET products to be sure that the Error occurs.
There are other products that still work so make sure they test with QWEET.
I think we may know what’s causing that particular issue with that specific prcpart in question.
You seem to have a config setting turned on that’s automatically skipping quote worksheet creation by default:
This would explain why those quote worksheets are being skipped and the system is having you generate those by clicking the ‘Here’ button. Is there a particular reason that you have that specific config setting activated?
If you don’t need that turned on, you can turn that off and try generating a test quote to see if that resolved the issue.
I’ven talked to engineering and they have a hotfix built out to correct this particular issue. It should be in hotfix and in your environment within the week. Please test turning that config off, and seeing if that resolves the issue you’re having with quotes associated to FIGQWEET.
Hi,
I cannot remeber setting that config explicitly. I thought that was default behaviour.
However I have scenarios where it is benefical for me to skip sub assemblies so I think I want to keep that setting.
However I clould try to change it just to see if it gets me through the day…
Checking in here to make sure you received the hotfix that corrected the 500 internal server error you were receiving when trying to generate those quote/bom worksheets that were skipped via the config setting.
Are you still running into that issue or has that been resolved? Please let me know!
Hi,
It seems to be gone.
But we shifted our production to products that did not have that issue for the time beeing.
I was waitng for some update on this topic before I did more testing.
I will try to get around to making tests today and get back to you.
Well we’ve got the 500 internal server issue corrected, but it looks like you’re running into another issue there when trying to create those orders… apologies there I know that’s frustrating.
Could we perhaps set up a screen share today to walk through that with you? I’m working on testing this right now in a backup environment to see if I can reproduce the same error that you’re receiving.
If you’d be able to set up a screen share please let me know and I’ll reach out to you via email directly.
Thanks for hopping on that call with me. We’ve got this reproduced on our end, and you/myself worked through a temporary solution that should keep you moving forward in the mean time.
I’m going to reopen this ticket thread on our end and coordinate the results that we found with engineering. I’ll be in touch with an update as soon as we’ve got a resolution here for you.
I did some more testing and interestingly enough quantity 11519 works also.
I tested 9000 and 10500 and 11519 and they all work.
But here is the real kicker …11521 also work!
So it seems like basically any number but 11520 will work. (maybe not, i cannot be bothered to test all numbers )
So there is something for engineering to get stuck into.
I would guess that there is something in the DB that has some sort of junk in it with relation to the number 11520.
This is by far the most common QTY we produce. So maybe there is a old BOM worksheet or somehing that is lingering in the DB somewhere and messes things up.
I’ve got this case built out with multiple test runs on numbers here that we walked through, and I have that sent over to engineering.
They’re going to evaluate/review the situation here, see what’s causing this particular error to populate for the qty of 11520, and send this back my way.
Once I’ve got that information I’ll reach out here and provide an update for you.
)