Latest Contributions by JakubSisak

@Kory - it may have been resolved in 2.1 but the bug has been reintroduced in 2.3. I am on 2.3.2. Offset value offsets labels on the north and west differently then east and south.  This is especially apparent when east and west labels have a vertical orientation and north and south labels have a horizontal orientation. there is also something wrong with the offset value text box - it must loose focus to accept a new value otherwise the value entered offsets labels to incorrect value.  The only workaround that works is to have 2 grids; 1 with north and west labels the other with east and south labels.    ... View more

Still doesn't work in 2.3.  I suspect map image layers (tile cache, not dynamic) is not supported. The workaround, instead of overwriting, would be to delete the service, then delete the cache folder on the server (\arcgisserver\directories\arcgiscache\yourtilecache) then publishing the service anew... ... View more

This is driving me crazy! The workaround is to have a lot of patience and drag the individual items manually and wait for the snap line to appear. Doing this 30 times isn't fun.  ... View more

Yep. Can't believe this is not possible yet. (running 2.3 beta) ... View more

same error here. this is not working. works on a simple scenario when a feature class is published from a desktp file geodatabase but when publishing services as references on an enterprise SDE, the Geometry($feature) object is null and has no members (X, Y, Z) and therefore cannot be used to obtain any values from the geometry of the feature. ... View more

OMG, This is soooo messed up...  I did not see this problem when working with small layout sizes such as letter or tabloid. As soon as I put a grid on an Arch D size, I was having very very difficult time adjusting offsets and the length of tics. This is a bug for sure. If ESR had a better way of reporting bugs (Click on a report a bug link, describe the problem, submit) i would have reported it but I could not bother going through the insane process.... This thread confirmed that I was not loosing my mind and that Pro is still very much an Alfa release but also pointed me to a kind of a workaround:  In my case - click on the Grid in the TOC and adjust offset - only once and tab away. Then click on the map frame to deselect the grid on the TOC then come back in and adjust another value - either change the offset again or change the length of the tics.  You can only change 1 single value at a time otherwise the grid items will go all crazy or become non-responsive.  adjusting 1 property then getting out of the grid properties and clicking on another TOC item then getting back into the grid proerties and repeating this one value at a time is highly annoying but worked for me.   ... View more

Maplex works fine and places everything perfectly. The problem is when labels are exported to static annotations. - most labels area dropped when the Contour Placement method is used.  ... View more

I now believe that it is specifically the contour placement method that's the culprit. It labels fine dynamically but when exporting to static annotations it drops (in my case) 73% (a VAST majority) of the labels. Also, the problem seems to get worse with the number of contours; the more contours I need to label the less exported static annotations I get. When the dataset contains up to 15000 contours and the Countour method is selected, the export will still drop labels but not as many. When labelling 50000 contours only a fraction of the labels convert and so on...    Workaround: Changing the method from Contour placement to Regular placement method retains ALL the labels in the same positions but you loose the nice laddering options.   In case anyone wonders why i need to label so many contours; we're building a high quality topographic basemap for a web GIS system across a vast geographical area and at 14 different scale levels down to 1:1500. At each scale level the interval of the contours changes and each scale level is more and more details as we zoom down. I need static annotations because we are masking the lines bellow the labels. Once finish we export these projects into a tile package to be used as basemap services on the server.  ... View more

I think this is a bug. I am running 10.6 and have the same problem.  Maplex is placing labels great but when I export them to annotations, most are missing and the Maplex placements are not honoured also. Laddering for contours which works great dynamically does not export at all into static annotations.  Seems like exporting is messed up.  ... View more

Sigh... It's March 14, 2018, we're on release 2.1. 2 and I just came across yet another obstacle and learnt that pie chart symbology is not yet available. We try so hard to migrate but there are still so many walls and performance issues. Labelling, symbology, editing, updating web services, customization  - all missing features and slow performance. So many issues and bugs it's totally killing my Pro experience. Pro has been in development so many years and now we know for fact it is the new desktop GIS replacement (something we've been told over and over wasn't the case) and at 2.1.2 this app is at an Alpha-level release at best. Until all ArcMap functionality is truly available in Pro including the ability to transition/import Add-In projects it will just not do.  ... View more

Short term solution without AutoCAD - install DWG True View (an official Autodesk DWG viewer), convert the file to 2013 version. This will also handle all X-REFs and other references and downgrade all to whathever older version you choose.  Backup your original 2018 DWG before converting.  ... View more

I believe OP is referring to the ability to overwrite Cached Map Image Web Layer which cannot be overwritten on Pro so long there is an existing Cache on the server.  The only option right now is deleting the service reference in portal, then deleting the service itself for (in Server Manager - not stable) or more reliably in ArcCatalog which works better than Server Manager for these sort of managerial tasks. Unfortunately, here we are using "legacy" tech. It's not possible to do all this in Pro? ... View more

Does anyone know when will this be introduced into Pro?  In my Migrating from ArcMap to Pro course in Sep 2017 the instructor mentioned that ESRI is expecting that Pro will match all ArcGIS Desktop (legacy) software functionality by the second quarter of 2018.  Does this include all Distrubute Databases functionality including replication/synchronization, etc?  Seems that the the old SDE approach is being pushed to the back burner a bit in favour the new data stores solution.  It's good but still too simple. If only there was a way to replicate/ synchronize published feature services to a remote multiuser geodatabase/data stores and push changes back and forth.  ... View more