Latest Contributions by JoeJoyce

‎05-25-2017

I need editable grids and could not find the Editor mixin for dgrid while dgrid1/Editor did exist. But I see in dgrid documentation now that it was only converted to a mixin in 0.4. So I think I should be able to use the old dgrid with the old editor now.

‎05-24-2017

I have several widgets that were using dgrid1 with dstore but the Attribute Table widget uses dgrid and dojo/store. It seems there can be a conflict with the two versions. When I open the Attribute Table widget, the grid data in my other open widgets using dgrid1 gets cleared. The rows just get deleted. And sometimes I'll see errors related to Store mixin in the console. It seems when the dgrid script for the attribute table is loaded it overrides the script functions and names for dgrid1 globally. But maybe I'm just doing something wrong. Is it possible to have both versions of dgrid referenced by separate widgets in the same app or do I have to downgrade my widgets to use dgrid and dojo/store in order to use Attribute Table? If not, is there a plan to migrate the Attribute Table widget to dgrid1 in the near future?

‎03-08-2017

I don't think that will work for me. I would have to update listenWidgetIds property before every fetch to make sure only the caller is receiving the data. I want all my widgets to be able to get data from widget A but I only want a widget to receive the data if it is the source of the fetch call. I'm just going to use the WidgetManager to get a reference to my A widget and then directly access properties that I set on it. var widgets = this.appConfig.getConfigElementsByName('MyWidget'); var widgetId = widgets[0].id; var myWidget = this.widgetManager.getWidgetById(widgetId); // Access data of widget directly var data = myWidget.someProperty; // use data...‍‍‍‍‍‍‍‍‍‍‍‍‍

‎03-08-2017

Hmm still happens. Does it matter that C had called fetchData(someWidgetId) in the past before B calls fetchData(someWidgetId)? It seems C is now subscribed to receive data whenever a fetch is requested for A.

‎03-08-2017

I have a widget A that publishes data and two more widgets B and C. When B calls fetchData for widget A the onReceiveData events fire for both B and C. Is that supposed to happen? I would expect only B's onReceiveData event to fire since it is the one who called fetchData.

‎08-06-2015

I have a query layer published in map and feature service. When I try to add a new feature using applyEdits on that layer I get this error in the log. Database error: Underlying DBMS error[[Microsoft][SQL Server Native Client 11.0][SQL Server]The column "..." cannot be modified because it is either a computed column or is the result of a UNION operator.]. I removed that column from the query but I still get that error. Is there any way to get the feature service to ignore that column when editing? I'm not sure why it is accessing that column in the first place since I didn't reference it in the attributes object. Is there a workaround or does applyEdits currently just not work with tables that have computed columns?

Online Status	Offline
Date Last Visited	‎11-11-2020 02:25 AM

My Ideas

Latest Contributions by JoeJoyce

Re: Is it possible to use widgets with different versions of dgrid?

Is it possible to use widgets with different versions of dgrid?

Re: Is fetchData supposed to cause all listeners to receive data?

Re: Is fetchData supposed to cause all listeners to receive data?

Is fetchData supposed to cause all listeners to receive data?

Feature service layer with computed column

Re: Is it possible to use widgets with different v...

Re: Is fetchData supposed to cause all listeners t...