I put this in the feedback tracker, because  I cant find any information on possible resolving this issue in the future. I also comment it in your thread on help with DAZ clothes (bad place to do that, sorry).

But I guess there is nothing bad in telling an old story again. It seems so old question that in the future we can freely call it "Jaws". ))

"Importing fbx file into 3dxchange pipeline (previously exported from DAZ with facial mocap data on it) and accepting automated bone structure conversion, resulting with jaw not mapped warning. After manual mapping nothing could be accomplished, head is moving, but jaw isnt. Its working fine only if you don't accept automated conversion on import, which obviously means that there is nothing wrong with DAZ character, neither with it export (regardless fbx 2011 or 2012 binary, or Reallusion duf file updated, or latest DAZ beta 4.11 update), but with 3dxchange.
More to that, if you try to place any third party facial mocap on any human model (say Reallusion CC3 base model for example), it is impossible to done inside of 3dxchange, because mocap output data in fbx format is unconvertable, only pz2 file through the DAZ export, which becomes the circle with no way out.
In order to work with avatar and not with iProp exported, automated conversion should be fixed in 3dxchange, but is not.
Of course, those who can efford to purchase Faceware and other Reallusion dependences  can close this workflow inside Reallusion product line.

But, hey, 3dxchange (in Reallusion own words) suppose to be open doors to 3d world, not the closed one.
Maybe I am wrong in everything I said, but surely many similar threads confirming this as a big 3dxchange pipeline malfunction.
I still didnt find any reply on this issue with solid resolving proofs, or staten resolving promise." 

Thanks

Intel Core i9-7920X 2.90 gigahertz
Intel Optane+1.8TBSSD
64 GB RAM
NVIDIA GeForce GTX 1080 Ti  11GB
Windows 10 Home (x64), Iclone 7, 3DXchange pipeline 7