POST
|
I just created a "shared theme" for my organization in the AGO settings. Now when creating a new WebApp Builder application, the Theme tab is blank. I would understand if the setting of a shared theme would not allow for any changes to the Style section, but why can I not adjust the Layout or most importantly switch between themes? I now seem to be restricted to the "Foldable Theme". The documentation I've read about setting up shared themes states that it will become the default but can be over-written by the user if they desire. Is this a glitch? The problem only affects newly created apps and simply removing the shared theme does make these settings reappear when creating a new app.
... View more
09-14-2017
06:01 AM
|
1
|
2
|
505
|
POST
|
Thanks for the tip. I was able to accomplish getting a null value using this in the Value Info field: IIF([STATUS]=2,"<Null>",[DIAMETER]) I have the rule set to run on attribute change, so it is a bit weird that as long as the expression rings true it will constantly overwrite any changes I attempt to make. I was originally hoping to use FIELD_TRIGGER because it only runs at the moment the specific field is changed. EXPRESSION will run anytime I change any field, as long as the expression is valid. I guess I could move it to manual-only. I will have to play with it and see what works best. Thanks, Phil
... View more
05-24-2017
06:16 AM
|
0
|
2
|
955
|
POST
|
Michael Miller is there any plans to introduce the ability to add null values? I came across an old thread where you considered adding the ability to use FIELD_TRIGGER for dates https://community.esri.com/thread/62983
... View more
05-24-2017
05:20 AM
|
0
|
4
|
955
|
POST
|
Thanks for the suggestion, although it didn't work. Attribute Assistant is a strange beast. There are a few instances where it reacts to VB syntax, but in this case, the value info field seems to be treating everything as straight text or numbers, not code.
... View more
05-24-2017
05:09 AM
|
0
|
0
|
955
|
POST
|
I am using the Attribute Assistant tool to automatically generate values for certain fields using the Value Method FIELD_TRIGGER. I'm running into trouble when I want to use FIELD_TRIGGER to change the value of a field to be null. I have no problems writing a rule that generates a regular string or number value, but I can't figure out how to generate a null value. When I use the Value Info of "Field Value|Field to Change|<Null>", it will put "<Null>" into any string fields I write the rule for, but I don't think this is a true null value because it doesn't work on number or date fields. I have tried countless variations on <Null> (<null>, "<Null>", null, isNull, etc) and none of them work. After reading the documentation on Attribute Assistant, it looks like FIELD_TRIGGER might only return a number or string value. Has anyone figured out how to return true null values for fields using the attribute assistant? You can see my specific rule in the attachment.
... View more
05-23-2017
01:05 PM
|
0
|
7
|
1789
|
Title | Kudos | Posted |
---|---|---|
1 | 09-14-2017 06:01 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|