Latest Contributions by DavidSolari

That'd be much better than fiddling with the calendar widget for me. Is Ctrl+; and Ctrl+Shift+; free? Those are the Excel binds so that'd make the UX even smoother. ... View more

ESRI screwed up the Field Maps update and it assumes all feature forms have the fancy new attachment items, which require upgraded attachments. If you can run Upgrade Attachments on all your tables without breaking anything, get that done. If you can't, call up your support rep and work with them to escalate this with Esri Inc. ... View more

I did a bit more testing and it looks like my chosen action (flash the data on the map) is actually working despite the error. Is this a benign error for all actions? I'd prefer not to dump weird errors into the console every time a user runs a task but that's better than not having it work at all. ... View more

Biggest thing that sticks out is: WARNING 003414: dataset does not match schema and will not be appended Did you try using the Append tool's field map option to assign the fields correctly? What you can also try is downloading the original data as a FGDB, doing the data design in another FGDB, appending the old data into the new schema, then publishing that as your service. That way you can check the validity of your data before it has to deal with ArcGIS Online. ... View more

Ah, there's always something buried in the support code! I'll have to test this later but I think this does the trick: /** Scale a point symbol and return the original and new sizes. */ export async function scalePointSymbol(point: Graphic, to?: number, by?: number): Promise<[number, number]> { if (!to && !by) { throw new Error("Must provide at least one of \"to\" or \"by\""); } let prevSize: number; let newSize: number = to ?? undefined; switch (point.symbol.type) { case "simple-marker": case "point-3d": prevSize = point.symbol.size; newSize ||= prevSize * by; point.symbol.size = newSize; break; case "text": prevSize = point.symbol.font.size; newSize ||= prevSize * by; point.symbol.font.size = newSize; break; case "picture-marker": const w = point.symbol.width; const h = point.symbol.height; const isWider = w > h; prevSize = isWider ? w : h; if (newSize) { point.symbol.width = isWider ? newSize : newSize * (w / h); point.symbol.height = isWider ? newSize * (h / w) : newSize; } else { point.symbol.width *= by; point.symbol.height *= by; newSize = prevSize * by; } break; case "web-style": point.symbol = await point.symbol.fetchCIMSymbol(); case "cim": prevSize = getCIMSymbolSize(point.symbol); newSize ||= prevSize * by; scaleCIMSymbolTo(point.symbol, newSize, { preserveOutlineWidth: false }); break; default: throw new Error(`Graphic does not have a point symbol (${point.symbol.type})`); } return [prevSize, newSize] } ... View more

There's at least a few of them ... View more

Webpack describes HMR on their official site as bypassing browser reloads entirely: you hit save, the page hotswaps the webpack chunks, now your webpage has the updated code ready to go, like "changing styles directly in the browser's dev tools." It also mentions this is something the "application" has to manage, which I assume is Experience Builder in this context, so we'd need someone with tons of internal ExB knowledge to weigh in on if this is feasible or not. ... View more