Issue: Cannot assign AS View Only to a user who has a Customer Community Plus user license.
Cause: The AS View Only permission set gives View All access to some of Accounting Seed's custom objects. The Customer Community Plus licensed user cannot have View All access to any custom objects. This is a known Salesforce Issue: https://success.salesforce.com/issues_view?id=a1p3A0000018BfNQAU. If you click This Issue Affects Me you will be notified of updates as Salesforce works to resolve it.
1. Clone the AS View Only permission set.
2. Remove the View All setting from all objects.
Issue: When applying cash receipts to billings, we are getting this error:
Insert failed. First exception on row 0; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, The transactions were not created after posting the billing cash receipt record(s)
Cause: This is a sharing and visibility issue. The error appears because the user who tried applying Cash Receipts to Billings does not have the necessary permissions to all of the necessary objects.
Resolution: The best way to resolve this is to assign Community users to Accounting Seed's permission sets. See Accounting Seed's Standard Permission Sets (Objects)
Question: Our Community users are unable to use Accounting Seed's objects, such as Time and Expense Entry, to register their times and expenses reports. Do they need any kind of license from Accounting Seed?
Answer: Any community user who is expected to use this functionality needs to be assigned an Accounting Seed license. Typically, our clients who use Accounting Seed's features in Community purchase a site license.
Question: Time Card is exposed in Community but the New and Edit buttons are not showing. Why?
Answer: Our 'New' button on Time Card is overriding a standard Salesforce 'New' button. Whenever you override standard Salesforce buttons they do not show in Lightning. Please see discussion here: https://success.salesforce.com/ideaView?id=0873A0000003X17QAE. We plan to create a brand new 'New' and 'Edit' button, without overriding the standard buttons, to address this issue in one of our upcoming releases.