Search found 2192 matches

Hello.
Could you please clarify what exactly is reproducible on our demo? Which print settings do you use? Do browser print preview settings match ones you used? Specifically, paper format and orientation.

Hello. Export server is not really a production-grade solution. It misses many features such as authorization, authentication, caching, etc. It is merely a demonstration of the protocol used by the client side. Usually, when such questions arise, we recommend implementing own solution to match one's...

This issue was fixed by this ticket: https://github.com/bryntum/support/issues/7695 Have you tried release 5.6.0?

Hello. As you noticed, applyChangeset API does not keep local changes. Alternative applyProjectChanges was supposed to do that, but it does not behave according to expectations, so we opened a ticket to change it: https://github.com/bryntum/support/issues/7819 You can try the following: enable STM a...
There was a misunderstanding, LWS is actually enabled in our org. However, our org uses debug mode which makes component functional in Firefox. If we disable debug, cell editor breaks in Firefox (works in Chromium-based browsers). There is a ticket to investigate it: https://github.com/bryntum/suppo...
I tried steps you described here and couldn't see a problem: Reproduce: Start Client and Export Server Change Zoomlevel to 1hour steps Click on Export Select date range 08/16 to 08/17 Export. Should look like attachement Could you elaborate on steps? Also, which export server version do you use?
Hello. How do those LWC communicate? Do they individually save changes to the salesforce backend and then another LWC gets notified? If so, you can try using https://bryntum.com/products/gantt/docs/api/SchedulerPro/model/mixin/ProjectChangeHandlerMixin#function-applyProjectChanges method. It allows ...
region is our term which is synonym for sub grid: https://bryntum.com/products/gantt/docs/api/Grid/view/SubGrid#config-region but why not make this the default behavior? That particular config cannot be made default, because it would break exporting overflowing columns. As I mentioned, it only work...

You can actually achieve expected result with a config:

features : {
  print : {
    keepRegionSizes : { locked : true }
  }
}

This way print feature will prefer region size to configured column width