@ssabo sorry, for the late reply! Yes, FSM6U24 supports Android 7 through 13. I just tried to access the internal storage with FSM6U25 with my Android 12 phone - all working fine! I know, it’s not the same setup as yours but I would assume this should work with your FSM version / Android version as well. I’m not sure regarding the manifest, as I’m not a developer. Have you tested this on other FSM version / Android version combinations? EDIT: Storage permissions aren’t provided explicitly for the App. Best regards Roman Android SDK > targetSdk will need to be 33+ for new apps and app updates by August 2023.U24 - <uses-permission android:name="android.permission.MANAGE_EXTERNAL_STORAGE" android:minSdkVersion="30" android:maxSdkVersion="30" /> <uses-permission android:name="android.permission.READ_PHONE_STATE" android:maxSdkVersion="30" /> <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" android:maxSdkVersion="30" />&l
@ssabo Hi, please check this thread for more information on the SDK-level: Best regards Roman Were you able to review the last reply?
@ssabo Hi, please check this thread for more information on the SDK-level: Best regards Roman This mentions that the SDK level is not setup for Android 14, The Manifest file show the permission requests will not be presented to users of android 12 or 13, which to my knowledge are currently supported releases, breaking the ability to attach files from local storageSDK Platform release notes | Android Studio | Android Developers
See below
Hi, did you give the app the required / requested permissions? Best regards Roman Yes, It does request permission to use the location while the app is running. One thing I did notice was in the AndroidManifest.xml For the location services no max SDK level is listed, so the app prompts to request that permission upon opening, additionally no max SDK level is listed so it is forward compatible as SDK levels are updated with android releases.<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" /> From my understanding this would mean the App no longer requests permissions after the listed SDK level, so for android 13 users (SDK version 33) no prompt or ability is available to assign manually, or request that permission when the application is opened for the following permission sets (and a few more). This would properly explain not being able to access internal storage, save attachments locally or pull a PDF from the phones storage to be used as an attach
app param was missing attachment directory
attached Screenshot
We’ve had the same issues since U23, even when attempting to adjust the layout via the print prompt it reverts before printing, this sporadically impacts about half of our reports. Would love to know the answer as well!
depending on your version - an import export map using the table person_cal_except might be ideal
@ssabo , Could you please try and check whether user_log_in.person_id works? Thanks, Hasara Unfortunately this does not work as the description noted
I’m guessing you modified the Delivery Method of the sync rules. Since those baseline views have no modified_dttm, the delivery method must be Batch - All. You cannot modify the baseline views because the next time you upgrade your changes will be overwritten. This makes sense! thanks!
UI Designer -> Right Click Button -> Set Perform Message to get this dialog box:
@ssabo How are you passing the perform message on the button?? Is it through the Perform message editor on the UI designer? Passing the information using the set perform message on the button in UI Designer
ensure first you can query the newly added table using the SQL Query tool, you may also need to refresh cache. When creating a new screen in ui designer you are prompted with: Select the primary table to be your newly created one.
from the custom metadata menu create an entry with the table name, and define each field. once done press load messages
Hey @ssabo Can you please specify the screen and the fields? A screenshot would be very useful as well. Cheers! line 2: 95.62 but maths = 95.625 It sent 95.63 over to the o_m5 table. It’s office spacing me.
I found the answer
It seems like the behavior has changed - The reports section allows you to set and configure a default printer per report, rather than system wide. It’s still strange that the original print dialogue is not triggered upon an attempt to print a report within another workflow. - Still don’t have an answer why. Only after configuring a default printer per report (with enable direct printing) the report is actually sent to the printer. The FSM Server user is also an AD user with valid credentials (apart from the client user). The log showed:Executing BusinessServerObject.InitThread > [Metrix.BusinessServer.BusinessPolicies.SharedTablesComponent.PrintReportManager]:Void
Self resolution: The quote was created prior to the pricing change, then flipped to a request after. We had applied a discount to the place as the alternative to managing the initial pricing rules. When it was flipped the already discount price, had the place discount applied.
Hi @ssabo , Following are the main types of Codes available in FSM. Code Tables : You cannot add a new Code Table, but you can add/delete or update a new record to an existing code table. Global Codes : You can add a new Global code, also you can add/delete or update a new record to an existing Global code. FSM Codes : You cannot add a new FSM Code, also you cannot add/delete or update a new record to an existing FSM Code. Hope this helps! Cheers! :) Is this something that has changed between 577 and 6? As you can see in the screenshots our 577 environment does has a new button on the code table screen. Wondering if this is a change in behavior or some custom config
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
