go for it mate 😉

* disclaimer…. Author of https://addressbar.info 😉

?:)

I would do a check on the query whether it returns the records in the first place.

When I deploy the bot to azure, I take error which is “There was an error sending this message to your bot: HTTP status code MethodNotAllowed”. I wrote MicrosofAppId and MicrosoftAppPassword to my code.

I am waiting your response.Thanks a lot.

Object reference not set = null exception. so, check whether the expected thing has value or not

Nice job, congratulations.I take error which is “Exception: Object reference not set to an instance of an object.
[File of type ‘text/plain’]”.Is there any suggestion about this error?

Hi Lukasz.

I haven’t tried with the offline sync. Sequence might be skewed on the offline scenario, where the actual request is happening when it’s syncing to the server. Duplicates I think will less likely to happen, as the sync is happened after the fact.

Great stuff. Do you know how this works in conjunction with offline sync. Especially in the sequence number scenario?
Does it create new numbers on sync or leaves potential duplicates.

if I understand your question correctly, you want to run an on-demand workflow against a list of contacts in a spreadsheet.

Then there are a few options here:
1. use SSIS + Kingswaysoft, use excel data source and use KingswaySoft destination to execute workflow based on the contact id.
2. Use a temporary entity in Dynamics where you have a lookup to contact (to resolve based on the contact id) and then run the on demand workflow against them. once finished, delete the records.

Seed is not solution aware, you might need to readjust the seed in the next environment. Here is an excerpt from Jonas’ finding: Note that setting the seed only changes the current number value for the specified attribute. It does not imply a common start value for the attribute. Thus the seed is not solution aware to be transported between environments. To set the starting number after a solution import, the `SetAutoNumberSeedRequest` must be called in the target environment.

AFAIK, no. It applicable to all records. 3rd party solution might be able to do the conditional one.

good suggestion, I haven’t tried that operator before.

When you edit via portal, you edit the Localised record, but in the CRM interface, you can only get to the Localised one via the ‘outer’ one which looks practically identical.

A good test for whether you’re on the actual page or the ‘page wrapper’ is if in your 3rd screenshot you click the ‘Web Page: Information’ dropdown and change to ‘Content Page’.

If that does nothing, you’re on the outer record, if it takes you to a page where you can edit the HTML, you’re on the right one.

Here you go: https://1drv.ms/u/s!AmGPnMIXbfFM02AekoGnlALClT7b

Thank you very much for your assistance. It appears this solution didnt like VS 2017. I installed everything following the instructions and using VS2015 and i can now see the connection type in connection manager.

had the same issue lately. Reinstalled KWS, then it showed up.

I have both the VS 2015 shell integrated and VS 2017 installed. I couldn’t locate SSDT for VS 17 so I ended up with SSDT for 15. Also installed KWS (all options) but like I said, the connector would not appear. It would have been nice if the KWS instructions on their site were more detailed. I’ve never used it before and their documentation reads as though the user already knows what to do.

What version of VS are you using? Have you installed the SSDT for the VS version that you are using?
VS 2012 or later will recognise the toolkit straight away. And please cross check the Kingswaysoft website, this article was written 3 years ago, things might have changed

Hey Andre, thank for your hint! I’ve deactivated a plugin running in the background and import worked. Best,
Johannes

Hi,

The error that you’ve got seems to be a null exeption. Do you have any plugin that runs on the entity? It might expect a value for a field but somehow missing from your source environment.

Hi Andre,

Yes that’s right we have written a plugin for automation and checking for any conflicts. The changes are being documented but I am afraid that once MS adds the capability to revert the approved time sheets we should be in a position to bring back the PSA to its original state.

Thanks for your efforts and guidance. Appreciate it and will keep following for more updates.

Thanks for providing more details of your situation.

Given the situation that you have, it means that you are intercepting the normal flow. Treat PSA as an Add-On XRM solution. So, you can customize it to meet the requirements, there are a few things that you will need to consider when customizing PSA:
1. Make sure you have a good documentation of the changes, as any future release of the product might change some stuff that you customised.
2. To address some of the automation requirements, you might need to create plugins/custom workflow to accommodate the creation of records, such as the project contract and the contract line. – Again make sure you also test the process to make sure there is no conflict with the OOTB PSA plugins and WFs

I found it quite challenging to customise PSA at this moment, due to the number of documentation that is still minimum. Particularly around their OOTB Plugins and WF where some of them are not giving a meaningful name. Pretty sure in the future, it will be well documented. But for now, my approach is through observation + trial & error.

Hi Andre,

Thanks a lot for your response. And just to give you a quick overview: We have been asked to setup PSA as just a reporting tool without leveraging the features, and the bitter part being time sheets flowing in from a different system without using PSA. So the integration will create timesheets and PSA will reflect the project values accordingly. So no project management , resource management and its just to show the project status

1. -> Sales price is calculated from the price list (with the context of Sales – a good explanation about sales price list: https://neilparkhurst.com/2017/01/21/psa-sales-price-lists/) that is tagged against the opportunity.
– Yes was following the same but thought to understand how does it work for multiple price lists for the same project in a financial year. The user is looking to have the bi annual price lists let me play with it

2. I’ve never seen any duplicate project tasks being created. Did you do some customization here?
– It doesn’t show in the UI but in the back end hope there are duplicate project tasks created when roles/resources are mapped as an OOB behavior. Came to know during import

3. based on my understanding, the price list is derived from the opportunity -> quote -> contract. Then the revenue will be calculated from there.
– Yes you’re right but the user is looking at PSA as just a reporting tool and doesn’t want to create a opportunity,quote instead straight away create a project contract (order) and project contract lines (order line) just to calculate the actual revenue.

4. I’m not sure what is the Audit contract that you mentioned here. Is this your own custom entity?
– Sorry for being over excited and missing to mention the proper names. This is the Project Contract (Order)

5. I’ve never used the journal lines for reporting and not sure about this. So, I can’t comment.
– Understand but I had to use. The time sheets that are submitted but not yet approved are stored as Journal lines

6. same here on the Audit Contract, not sure what is the entity that you are referring. Contract lines creation will inherit if you follow the flow: Opportunity -> quote -> contract
– Yes this is the problem. Breaking the flow and trying to jump in between 😦

hi Boopesh,

I’ll try to get based on what I understand from your questions:
1. The sales price of the resources will be calculated from the price list that is tagged to the project customer. For multiple price lists related it will take the first one. Hope Estimate Lines entity is saving this info
-> Sales price is calculated from the price list (with the context of Sales – a good explanation about sales price list: https://neilparkhurst.com/2017/01/21/psa-sales-price-lists/) that is tagged against the opportunity.

2. Duplicate project tasks (same task name) will be created when a role is mapped.
-> I’ve never seen any duplicate project tasks being created. Did you do some customization here?

3. Create a project contract and contract line mapping the project. Make sure the project price list for the contract has the roles with start/end date mentioned only then actual revenue will be generated. PSA pulls the price lists from the customer and creates a copy under project price lists.
-> based on my understanding, the price list is derived from the opportunity -> quote -> contract. Then the revenue will be calculated from there.

4. If the price list tagged to the customer is updated this does not reflect it in the project price lists under the Audit contract. We have to manually update it
-> I’m not sure what is the Audit contract that you mentioned here. Is this your own custom entity?

5. Since the approved timesheets cannot be backed off, we are using journal lines instead of actuals so that it can be revoked, considering the fact that graphs and charts should be updated based on custom fields using journal lines.
-> I’ve never used the journal lines for reporting and not sure about this. So, I can’t comment.

6. Can the creation of audit contract and contract lines be automated, will it reflect the same way as creating from the UI as not sure about the PSA framework which touches more tables.
-> same here on the Audit Contract, not sure what is the entity that you are referring. Contract lines creation will inherit if you follow the flow: Opportunity -> quote -> contract

On top of that, are you using the Dynamics 365 (Customer Engagement/CRM) or the ERP (AX)? Seems like your questions are not relevant to the Customer Engagement/CRM normal behaviour.

Thanks for the blog was looking for this sort of information. We are implementing PSA for a customer and facing a lot of issues, thought you can shed some light on me. Please can you let me know the below understanding is correct and anything that should be taken care of.

1. The sales price of the resources will be calculated from the price list that is tagged to the project customer. For multiple price lists related it will take the first one. Hope Estimate Lines entity is saving this info

2. Duplicate project tasks (same task name) will be created when a role is mapped.

3. Create a project contract and contract line mapping the project. Make sure the project price list for the contract has the roles with start/end date mentioned only then actual revenue will be generated. PSA pulls the price lists from the customer and creates a copy under project price lists.

4. If the price list tagged to the customer is updated this does not reflect it in the project price lists under the Audit contract. We have to manually update it

5. Since the approved timesheets cannot be backed off, we are using journal lines instead of actuals so that it can be revoked, considering the fact that graphs and charts should be updated based on custom fields using journal lines.

6. Can the creation of audit contract and contract lines be automated, will it reflect the same way as creating from the UI as not sure about the PSA framework which touches more tables.

Thanks,
Boopesh D