Best Of

Hi @User_HIG7E,

I hope you are doing well.

Since in your CASE WHEN formula, you have set the condition of CASE WHEN {transaction.type} = 'Invoice' - which means that this already looks for the transaction type of Invoice, you should select Transaction Number or Document Number such as for example: CASE WHEN {transaction.type} = 'Invoice' THEN {transaction.number} ELSE NULL END

or you can set a Criteria in your Project Saved Search to filter the Invoice transactions:

Then in the results, you can add the fields from Transaction fields…

Result:

I hope this helps! 🙂

==========
If you find this reply to your question as helpful, others with the same question might find it helpful as well. By marking “Yes” on the “Did this answer your question?”, you’ll be able to aid the community to find the solution much easier and faster without the need to read through all the replies

You can update the time entries to always be billable - using SuiteAnswer 102926.

Note that the project preferences themselves can impact the time entries. If the project preferences have 'productive' = true, the time won't be marked as billable on the time entries.

~angela

Hi @Bee Yook

You can use csv import. As explained in this thread.

There is another way is to use the [Duplicate Multiple Locations] button under the Item > location Inventory tab.

E.g. you can configure all the locations that you want under one item first. After that click this button to copy all the location settings for this item to other items. (Assuming all the settings are the same). You may want to test this out in sandbox first.

Regards,
Wee Ming

Well said/demonstrated, Jeremy Guimaras-Oracle

Nice

There has to be more than one unique value in one of the fields of data.

As example, if a contact has 2 addresses, 2 rows will be returned.

Criteria to only pull the Default (billing or shipping) address, would eliminate the 2nd address.

The same theory is true for every line of data.
If you have a multi-select field in your data results a separate line is returned for each unique field value. (All the data strung together on the "row" becomes unique when there is a "different" value in any cell/s)

Look at your criteria to fine tune your results. You could eliminate the field with multiple values or your criteria might only include one specific value, excluding the rest.

I find the culprit by putting the data in a pivot table, count on appropriate field/s then when the count is more than 1, investigate those rows of data to find the 2nd unique value causing the additional row returned then adjust your criteria or columns.

Best.

Option 1 would require selecting an Invoice rather than checking a box. Because any Vendor/PO can relate to any Customer/Invoice, it will be difficult to build logic to link them automatically.

Alternatively, your team can select the related PO when they are creating the Advance Invoice. That would also establish the link between PO and Advance Invoice and can facilitate the alerts.

Hi @Wee Ming

Thanks for that.

I will go with my workaround in that case of having a custom field. It's something I have had to do previously for sales orders because of the limitations around approval for that

Thank you, @Micah Timbol-Oracle!
That was my susupicion and thank you for confirming.