mbouchard Red Ribbon

Yes, we are still experiencing issues as well.

I am getting multiple complaints of slow page loads, but have not heard of any errors yet.

We just now got access to our production account. We'll be paying folks overtime to catch up :-(

I want to echo Chris' sentiments about these releases being performed on a weekday - that's totally irresponsible in my opinion as a 30 year IT professional. I always planned any major changes or upgrades to occur on a weekend, that's just common sense. This is the second release in the last year that has caused us…

Darren, you're not alone - we experienced the same thing. Had to go and edit the HTML to repair things, wound up using pre tags on some text fields to get it to work, but even that does not look great... I know I didn't catch all of the problems too, only the ones that were reported to me... I think we all have enough work…

I think your formula looks OK, except you are missing a closing parenthesis at the end. You may also want to round the result. Good luck!

I believe if you un-check "Records are Ordered" it will sort alphabetically by the Name field in the drop-down...

Thanks David, I see that does indeed allow it to work without error. That makes it a little tricky for my application due to timezones unfortunately, but I'll come up with a way to work through that. Thanks again, Mike

Thanks for the suggestion, but setting createpo to 'T' won't work, it throws the error 'Invalid createpo reference key T'. If I try to set createpo to 'DropShip' it submits successfully, but does nothing...

I never found a way to make it work and, sadly, had to have my purchasing department do them manually. If you have a preferred vendor and the item is set as a drop ship item the PO will automatically be created IF you are creating a new Sales Order, but I could not get a drop ship PO created from a pre-existing sales order…

Hi Andy, I've successfully inserted and removed rows from the itemvendor sublist, as well as changed the values of fields in existing rows, so I can say that it is possible and does work. Have to make sure to call nlapiSubmitRecord() afterwards... --Mike

This may sound silly, but you have GetLineItem.... but it needs to be getLineItem with lower case g...

Did you try using getLineItemValue() instead of getLineItemText()?

The script is tied to the case record. It is used to populate 2 custom fields on the case record. One is the top level parent of the customer, the other is the immediate parent of the customer. It is not a big deal, just checking to see if there was some other way to do this I hadn't considered. The current method is…

Thanks for the answer Evan - that does explain things. So there is no way to get the immediate parent using nlapiLookupField() then? Just wondering because I am doing this in a client-side script, and nlapiLoadRecord is a little inefficient to get that one value.

It may not make much difference in practice, but there is a definite difference in the amount of data that needs to be sent from the server to the client when calling nlapiLoadRecord (which returns all fields and sub-lists) vs nlapiLookupField (one field only). I usually try to transfer the least amount of data possible, a…

Hi Kent, I think that under the "Advanced Options" you just need to check "Overwrite Missing Fields". Then just include an empty column in your CSV file for the field you want to clear. Best Regards, Mike

Hi All, Was there ever a viable solution to this issue? We are running into this ourselves. Item drop-shipped to customer on a sales order, then returned to our warehouse with an RMA. Inventory increases but cost is $0.

We are having exactly the same issue as Sohail, and are going to attempt his work-around. But WHY OH WHY did this change all of a sudden with no warning? We have enough to do without fixing things that should not be broken!!!!

Hi - thanks for the responses. We tried enabling php_openssl.dll and copying the 2 .dll's, but it did not help. Any other thoughts? Thanks

I entered a case with NS support, they attached it to an existing issue they already had open: 286955 "Transactions > Financial > Create Revenue Recognition Journal Entries > Rev Rec Journal Entries are not Queuing and is taking a Long time to start." Supposedly they are working on it, not sure if the fix will impact the…

Thanks both for the replies/suggestions. I have recommended switching browsers with mixed results - some see a significant improvement, others do not. We have a geographically diverse team and there seems to be no rhyme or reason to the issue, but it is definitely impacting at least 25% of our users. We have heavily…

We are having the same issues - random people getting unexpected errors when trying to work with transactions. I was able to help one person by changing their role - but others with the same role were not having issues. Very odd and perplexing - seems to be more user related than role related for some reason.

Update: I was able to help another user with this issue - I created an exact copy of the role they were using and gave it to them. When they switched to the copy everything was fine - so that is a workaround. I just opened the role, changed the name and did a Save-as. Hope that helps!

By accident I discovered the solution to the problem. It appears that the smbXML import won't recognize an entity reference in an entityhandle or entityRef field until you have first performed an xml query that returns the entity. Sounds ridiculous, but I did confirm it by testing. To successfully import cases you should…

I'm having the same issue - sorry I haven't figured out a work-around either.

Seems to be working this morning.

Same issue here.

We're wrestling with the same problem now - looking at the PET score, the client times are awful in I.E. 11. Unfortunately some of our users are working with other systems that require I.E., so it is really killing them. Would be nice to know if there are some tweaks that could be made.

Likewise here, we were also upgraded over the weekend. Appeared to be OK earlier but bogged down to molasses now.