Some other binding possibilities

Posted by: saso.sabotin on 29 September 2017, 4:48 am EST

  • Posted 29 September 2017, 4:48 am EST

    Hi guys!

    Ok we are facing one big issue with Wijmo (it does not concern Wijmo core itself but only our internal system concept).

    So the main question is: Is it possible to bind the object’s property on some different way or is providing the string to binding attribute the only way?

    Why I am asking that is next. In order to populate our table (lot’s of data (20k), lot’s of columns (100)), we have to send, let’s say 5 REST calls, to the backend. So for each row we get 5 different objects, which we obviously have to merge, in order to get one row result. But the problem is that these objects can have the same property names, therefore it will overwrite them, so we lose the value of original object. So we would like maybe to bind columns to some function or whatever that could return the proper value from corresponding object (out of these 5 objects).

    Is there some solution for our problem or is that a no-go?

    Thank you very much in advance!

  • Posted 4 October 2017, 4:15 am EST

    Hello Saso,

    We are sorry for the delayed response.

    You need to provide object property name to binding property.

    The problem can be resolved by checking if the property is being added exist in the object or not. If yes, rename the property while adding in Object. You can change header later using header property.

    Thanks,

    Manish Kumar Gupta

  • Posted 13 October 2017, 6:08 am EST

    Not a problem!

    That was actually working but with big amount of data we get a memory leak easily.

    Therefore we used another solution. We some Column class where some data provider is referenced, from which we can then retrieve the unique data without extending the base object. So the value is actualy rendered with some getValue method and not item[‘directly’].

    Br, Saso

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels