> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/reporting-and-analytics/bevica_power_bi/bevica_power_bi_common_questions_faq.md).
# Bevica Power BI: Common Questions / FAQ
Common answers on measures, filters, dates, and dimensions in Bevica Power BI.
## Questions
### **Which measures should I use?**
* Most of the time you should use the Global Sales or Purchase Measures as they are simplest.
### **Which filters should I use?**
* On the operations model the key filters (depending on your version) are likely to be:
* **Transaction Source Filter** (ILE/Not ILE)
* This filters entries to be from the item ledger entries (ILE) or posted documents (Not ILE). The posted documents will be for line types of G/L Account, Resources etc.
* There is a global filter which is simplest
* There is also a filter within the ILE table
* **Item > Item Type**
* This is in the Misc. folder and allows you to filter to items (Inventory) or other types (e.g. G/L accounts etc.)
* If you're looking at item type transactions - e.g. inventory valuations or sales of wines - then you should usually filter to Item Type = Inventory. The Transaction Source filter above will also achieve a similar result (as only 'item' sales go through the item ledger)
* Dates - see below\...
### **How can I see how much freight was?**
* This will depend on your setup and modules used. But, add the Item Charge from the Item Ledger Entries as a filter.
### **Which dimensions should I use?**
* Dimensions exist on either the parent record dimension (e.g. Customer) and/or the Dimension Set Entries as the transactional dimension. So the answer is "it depends"!
* A relevant example is often where a salesperson changes over time.
* e.g. Customer A has Salesperson "BARRY" assigned and lots of sales. The Customer 'Salesperson Dimension' will be BARRY and (assuming dimensions aren't changed on transactions) the Dimension Set Entries 'Salesperson Dimension' will also be BARRY. If Barry leaves and "SARAH" takes over the account (and the Customers dimensions are updated) then the Customer 'Salesperson Dimension' will now be SARAH, any new transactions will be SARAH but any old transactions will still be BARRY.
* You can therefore create a report which might look like this where Sarah took over responsibility on 01/01/2023. The Customer SP Dim is the current dimension from the customer record, but the transactional one is at the point the sale was posted.
* | Date | Customer SP Dim | Transaction SP Dim | Sales |
| ---- | --------------- | ------------------ | ----- |
| 2021 | SARAH | BARRY | 1,000 |
| 2022 | SARAH | BARRY | 1,200 |
| 2023 | SARAH | SARAH | 1,200 |
| 2024 | SARAH | SARAH | 1,300 |
### **What dates are the relationships on?**
* Item Ledger Entry
* Posting date
* Customer and Vendor Ledger Entries
* Posting date is default
* You can use the **Date Type Filter (Cust/Vend Ledger)** to override this and use 'Due Date' or 'Closed at Date'
* You will want to use 'Due Date' when looking at aged payables/receivables usually.
* Open Orders (Sales and Purchase)
* Posting date is default
* You can use the [**Date Type Filter (Open Orders)**](/documentation/reporting-and-analytics/bevica_power_bi/open_orders_measures_-_sales_and_purchase_-bevica_power_bi.md) to override this and use the other types.
### **How can I report on Shopify sales vs. normal sales?**
Assuming you're using the Shopify extension **and** Bevica Shopify enhancements you can set a dimension against specific shops and locations. This dimension would then need to be one of your shortcut dimensions in General Ledger Setup.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.bevica.com/documentation/reporting-and-analytics/bevica_power_bi/bevica_power_bi_common_questions_faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.