1 - Try writing your report from a different focus point (contacts) with contact condition / then display opportunity fields
2 - Events report! We need this! As the “Status” of the Contact/Event sits inside the relationship table not the module tables AOR does not see it and will not report on it
That doesn’t work for Opportunities/Contacts, even starting from the Contacts module.
opportunity role is also a field inside the opportunities-contacts relationship table and it’s not available in reports
You can use any SQL query to set up the data, so that would solve your needs. Then you have plenty of chart types to choose form, or you can even display the data as a fancy interactive table. Great stuff you can do with that.
Well, we still use KReports 3.1 with some fixes we made, especially for (1) support of PHP 7.0 and 7.1 and (2) fix javascript errors with some translations.
We have no problems with that version.
If you are interested, send us an email at support at quickcrm.fr and we will send it to you.
Many thanks for the Kreporter 3.1 modules, I have used it and it works well.
I have subsequently made another version of KREST, that basically renames all of the Slim to Slimv2 to allow it to work with the newer Slim included with SuiteCRM (Im not using it in anger as yet until our client answers a few questions so I may still use Kreporter3).
If anyone wants the Bodged up Krest I have do let me know!
Ahhh that error is not a KReport problem, I have just installed a brand new 7.11 on Siteground and had that (the default permissions for a server like this seem to be insufficient).
Can you confirm your server set-up though becuase the KReporter requirements change a bit depending on the set-up (if you are using php-fpm or other proxy based setup there is a further requirement).
To start with (for testing), go to the /vendor and rename the slim folder to something like slim_old
go to the /KREST edit the index.php file and add this:
if (!function_exists('getallheaders'))
{
function getallheaders()
{
$headers = [];
foreach ($_SERVER as $name => $value)
{
if (substr($name, 0, 5) == 'HTTP_')
{
$headers[str_replace(' ', '-', ucwords(strtolower(str_replace('_', ' ', substr($name, 5)))))] = $value;
}
}
return $headers;
}
}
you need a css tweak so do this:
Add following lines at the top of of themes/SpiceTheme/extjs6/ext6_override.css
html{
height:inherit;
max-height:100%;
}
“Can you confirm your server set-up though becuase the KReporter requirements change a bit depending on the set-up (if you are using php-fpm or other proxy based setup there is a further requirement).”
Dont really understand this ? Its a basic empty suiteCRM on a 1&1 server…
I have tried the 3.1 Kreport cause I saw on another topic that the 4.2 do not work on suiteCRM, but I got a lot of error like this :
Uncaught SyntaxError: Invalid or unexpected token
at kreportsbase1.js:1
(anonymous) @ kreportsbase1.js:1
kreportsbase3.js:1 Uncaught TypeError: bi is not a function
at kreportsbase3.js:1
(anonymous) @ kreportsbase3.js:1
standardviewpanel.js:1 Uncaught TypeError: bi is not a function
at standardviewpanel.js:1
(anonymous) @ standardviewpanel.js:1
googlechartspanel.js:1 Uncaught TypeError: bi is not a function
at googlechartspanel.js:1
(anonymous) @ googlechartspanel.js:1
ksnapshot.js:1 Uncaught TypeError: bi is not a function
at ksnapshot.js:1
(anonymous) @ ksnapshot.js:1
kreportsbase5.js:1 Uncaught TypeError: Cannot read property ‘Toolbar’ of undefined
at kreportsbase5.js:1
at ext-all.js:38
at h.fire (ext-all.js:38)
at h.Ext.apply.readyEvent.e.fire (ext-all.js:38)
at fireReadyEvent (ext-all.js:38)
at ext-all.js:38
Dont rly understand … I will try u 2 piece of code with a re-instalation of the 4.2 …
But for now I got a 404 error on XXX.com/KREST/sysinfo
Its look like the rewriterules does not work or something like that …
The instructions I provided were for Kreporter 4. No idea about 1&1’s hosting sorry. However I had a load of 404’s on Siteground and its adefault permissions issue, you can search here to find out how to fix that.
It could be the redirect, but that code is unlikely to work:
C:/htdocs is a windows drive/folder (are you using a 1&1 windows server?)
You would usually put all of that in a in the core apache config (which is unlikely for you to have permissions for), you would then be adding other commands to the .htaccess.
However with most reasonable hosting this is already pre-working (most modern CMS’s require this functionality).