Check out the link below for more detail:

https://supportcommunity.zebra.com/s/article/Deploy-DataWedge-for-Android-Configuration-using-SOTI-MobiControl?language=en_US

You need to use the following post install script in order to get the .db to merge without a reboot:

__chmod 777 /enterprise/device/settings/datawedge/autoimport/datawedge.db

Hi Matt, 

That is the instructions I was following. My understanding is that the chmod needs to be done on the file I'm copying in there, not 'datawedge.db'. So I changed that to the file name of my profile. Other than that, did exactly as described below. 

I actually don't care about having to reboot. That doesn't bother me. What bothers me is that the profile doesn't work properly after it's auto imported. It does not fill the data field with the data it scanned. It clearly scans the data, bleeps like it does when it recognises the barcode, and then does nothing. 

As I said, when I import that exact profile file manually, everything works fine. 

If the import is working and you are seeing the Profile(s) in DataWedge then I would think something else might be happening that is isnt directly import related.

You have two different device models that are potentially running different DW versions. They may also have different integrated imager configurations available to them so I would consider having separate DataWedge configurations applied to each of them. I have seen issues with attempting to use the same DW config across different device models in the past. 

Also, are you testing under the exact same conditions? DataWedge is typically powered off of matching activity names and depending on how an application is developed it may have different activity names for different screens. A login screen when the app is first launch might have a different activity name than the main activity for instance. If there are differences then DataWedge behavior could also be affected. If there isn't an activity match then the default Profile0 usually takes over. Profile0 is configured for Keystroke output by default so if the field doesn't have focus then it won't receive scan data. Does the scan data get inputted into the field after tapping it? If so, its probably Profile0. Try disabling Profile0 and then see if the scanner is still accepting scans on the same screen. 

Well - I didn't manage to work out what was causing the issue. Ended up having to reinstall the profile once the device booted, and now left it alone. 

It's fiddly to say the least!