Posted 9 April 2018, 9:44 pm EST
Hi,
I’ve had several problem setting up the enterprise version of Wijmo and with the pager these times, as you may see [url=https://www.grapecity.com/en/forums/wijmo/typings-missing-when-going]here and [url=https://www.grapecity.com/en/forums/wijmo/odatacollectionview-editit]here.
So I’m still running a quite outdated version of Wijmo.
Now with the new key registration, it is (partially) going smoother.
But since then, the WjCollectionViewPager component seems to have ceased doing its job using an ODataCollectionView.
Here’s the code I used. Nothing transcendental, and the pager used to work that way with both ODataCollectionView AND regular CollectionView.
<wj-flex-grid #flexGrid
[itemsSource]="cv">
</wj-flex-grid>
<wj-collection-view-pager [cv]="flexGrid?.collectionView"></wj-collection-view-pager>
export class myComponent implements OnInit {
cv: ODataCollectionView;
constructor(private readonly articleService: ArticleService) {
}
ngOnInit() {
this.cv = this.articleService.getOData();
this.cv.pageSize = 15;
}
}
Now, it doesn’t anymore. It just displays 1/0 in the pager’s input and its buttons do nothing.
I went from a quite old version to the last one. My package.json went from :
“wijmo”: “http://prerelease.componentone.com/wijmo5/npm-images/C1Wijmo-Enterprise-Eval-CommonJs-5.20172.359.tgz”
to :
“wijmo”: “^5.20181.436”
Switching from one to the other resolves/recreates the issue.
I did not investigate any further ; if it worked, surely it should still.
For now, I still can’t deliver a registered version (though we bought a licence months ago) partly due to this issue, so any help would be really pleased.
Thanks a lot in advance,
Geoffrey
