Hello guys, I’m on the making custom report for my sales invoice per sales code (this made from classic custom field). Anyone can tell me why are custom report showing 3 lines whereas in my sales invoice only using 1 line for inventory item?
so, what I need? How to show only 1 item under invoice ref? and can I add sum feature to count every single invoice ref. to get figure out count of invoice?
This custom reports are needed to be shared for public that only can see their invoice based on their sales code (made from custom column). Any ide how to make a report that show invoice per sales code and user only can see their own sales code?
If I use advanced querries to accessing or filtering custom column (sales code) in sales invoice, it would give access to users to see all sales invoice, it would make users can see all sales invoice right?
If I use custom reports, I can create user ID for external that only can view custom report without access to click the number that linked to invoice but that user only can see the total of sum or total of count.
Please @lubos consider again to determine custom report as a obsolete because it’s very useful.
I’ve tried and it very nice, thank you. but @lubos said that custom reports would be obsolete soon, it makes me hesitant to use even though I need it to give access certain user but restricting them only can see sales invoice per their own sales code.
@lubos suggests to use advance querries, but it still give access user to see all sales invoice first before set up the advance querries isn’t it?
This is not possible. You also changed what you want now from what you stated in first post. So not clear what you really want. Please explain in detail with attempts you made and screenshots as per forum guidelines. Rather than asking is it possible, try it out in a test business. @Mabaega and @Tut gave you proper guidance.
I said that, it means work well.
Actually I need to give access for certain user to view custom reports. Custom reports give advantage that number showed is not linked to any transaction so that restricted.
@ejjaadiargo the use-case you have can be supported in advanced queries too. When I say something will be obsolete, I’ll just move it to obsolete features but you will be able to continue using it.