Best Of

Thank you Angela

Kits - by design - do not have a purchase price. This is why there is no field on the kit record for 'purchase Price'. There isn't a cost to kits specifically, the costs are assigned to the kit members. The purpose of a kit is to allow you to sell individual items and 'packaging' them together and apply a different revenue account. Since a kit is not an actual item, it won't report with purchase pricing.

To value a kit, you'll need to report on the kit members. The cost of the members drives the cost of the kit.

Item groups are a little different, in that the group components drive both the cost and sales price. These won't actually have costs/prices assigned to the Item group, again the cost will come from the Components.

The key here is that the components haven't been 'consumed' to create a brand new item - so reporting on them as though they are a 'new' item won't work. All reporting will have to come from the components.

I hope this helps.
~angela

Hello @Javier P.,

You may check the permissions for Warehouse Manager in this SuiteAnswers article: 9918 | Standard Roles Permissions Table.

I hope this helps :)

Generally Production environment is faster than Sandbox environment, is the Sandbox refreshed regularly, when is last time it was refreshed? also it depends up on the SuiteQL query and transaction data results count make the slighter performance difference, I am just suspecting in these areas, I am not sure fully, it may be helpful if you check on these, thank you

Thank you.

It worked,

Thanks for the clarification @Able Wilson.

This is currently not possible, even in Allow Period Changes = True and when we try to change the address from this original billing address:

To this new one:

And try to save this, the billing address is reverted to the original:

There was an enhancement filed for this under enhancement 383015 Edit Bill To Address or Ship To Address in Closed Period for Open Invoices but was since closed as a fact of life. As per SuiteAnswers 50589 "You cannot make a change in an address – whether Ship To or Bill To – if the transaction is already on a closed or locked accounting period."

If you choose to re-open your accounting period, please proceed with caution or please test it first in your Sandbox Account.

Apologies for this system limitation.

Hello @Adrian Romualdo-Oracle

The 2 documents that you provided are for inbound SSO to the web store. That would allow a third party identity provider to authenticate customers to our web store. We don't want that. We want outbound SSO so that our customers can login on our web store and then use that to authenticate to other applications. For example:

We have a custom application that lives outside of NetSuite on our own web server. When a customer goes to that app and clicks the login button, they need to be redirected to the SCA web store where they login with their SCA customer credentials, then get redirected back to the custom application and will be automatically logged in to the application.

This used to be handled by SuiteSignOn, but that is being deprecated and will no longer be available in a few months. The documentation says that NetSuite as OIDC Provider is the replacement for SuiteSignOn. However, the documentation doesn't give a lot of details about how to setup the user flow that I described above.

@BryanL Can you share the formula you are using? My guess is you add ".id" to the field you will not get that error.

@NSPK As per the screenshot you attached, I noticed that formula used in the both saved search [{fxamount} * {custbody_pcg_lvl_1_disc}] and Workflow [{usertotal}*{custbody_pcg_lvl_1_disc different}] are different.

Please make sure whether the formula in the workflow is correct.

Thank you