The 1C:Enterprise developers forum

#1
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Jul 20, 2011
Company:

I have a Report for Expenses by Counterparties and Contractors, which looks like the this:
Counterparty 1
- Goods Group 1 Supply Contract: 210
Counterparty 2
- Goods Group 1 Supply Contract: 130

And I would like to have a report looking like that:
Goods Group 1 Supply Contract
- Counterparty 1: 210
- Counterparty 2: 130

How can I implement this? Any ideas? The Data Composition Schema does not want to group contracts and gives the following best result:
Goods Group 1 Supply Contract
- Counterparty 1: 210
Goods Group 1 Supply Contract
- Counterparty 2: 130

 
#2
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Sep 16, 2011
Company: individual

It looks like you've named contracts by activites. And want to use them to group those activities. This is bad idea. Contracts represent actual agreements between your company and counterparties. To make the analytics which you want (GROUP BY Activity, Counterparty) you need to add the activity field to your documents and registers and build the report on that field. If it is urgent you can add it to the Contract catalog and use for reports as a first groupping level instead of the contract itself.

 
#3
People who like this: 0 Yes / 0 No
Just came
Rating: 0
Joined: Mar 5, 2012
Company:

I think you have two goods groups with the same name.

 
#4
People who like this: 0 Yes / 0 No
Just came
Rating: 0
Joined: Mar 5, 2012
Company:

can you give reference on the demo-base like this: http://apps.1c-dn.com/1cas/#e1cib/app/Report.BalanceSheet

 
#5
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Jul 20, 2011
Company:

Unfortunately I can not yet.

 
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)
Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.

/* Улучшаем читаемость списков в документации */ .workarea ul, .content ul { margin: 15px 0 20px 25px !important; padding: 0 !important; list-style-type: disc !important; } .workarea li, .content li { margin-bottom: 8px !important; padding-left: 5px !important; line-height: 1.6 !important; } /* Ультимативный фикс для всех уровней заголовков в контенте */ .workarea h1, .workarea h2, .workarea h3, .workarea h4, .workarea h5, .workarea h6, .content h1, .content h2, .content h3, .content h4, .content h5, .content h6, div[id*="content"] h5, div[class*="content"] h5 { display: block !important; font-weight: 700 !important; color: #005aa0 !important; /* Наш фирменный синий */ text-transform: none !important; margin-top: 30px !important; margin-bottom: 15px !important; line-height: 1.2 !important; font-family: Arial, sans-serif !important; } /* Принудительные размеры в пикселях (чтобы не зависеть от % или em) */ .workarea h1, .content h1 { font-size: 28px !important; } .workarea h2, .content h2 { font-size: 24px !important; } .workarea h3, .content h3 { font-size: 21px !important; } .workarea h4, .content h4 { font-size: 19px !important; } .workarea h5, .content h5 { font-size: 18px !important; } /* Для 5 решеток ##### */ .workarea h6, .content h6 { font-size: 16px !important; } /* Фикс, если Битрикс добавил лишние отступы перед списками после заголовка */ .workarea h5 + ul, .content h5 + ul { margin-top: 5px !important; }